5 ms·
Netlify Status – build pipeline down for past 4 hours
- AdamDKing 7y agoPossibly due to the current Google Cloud outage. https://status.cloud.google.com/incident/compute/19008 https://status.cloud.google.com/incident/compute/19008
- moocowtruck 7y agoi thought the entire point of the cloud was to make stuff like this not cause your site to go down, or did someone realize that only had to be part of the marketing
- AzzieElbab 7y agoexcrement does hit the air-conditioning time to time
- lykr0n 7y agoThe cloud doesn't go down- regions and services inside that region go down. A region (or AZ for Amazon) is no more or less reliable then your run of the mill DC
- jgalt212 7y agoTrue, but then the question is it cheaper to build your own redundancy or duplicate all/most infrastructure across multiple zones? Once that becomes the question, the cloud not longer looks so simple or cost effective.
- erikpukinskis 7y agoNo the point is when the cloud goes down you can stay in bed because someone else is sorting it out for you.
- sunasra 7y agoExactly for this, I have built https://IncidentOK.com https://IncidentOK.com which sends alert over email/slack to user if any third party services like this reports an outage or incident.
- jaysh 7y agoI regularly see your comment (or ones for similar services) on these types of posts. I assume the strategy is working as you keep replying, but have you considered starting posting yourself, as a measure of "you can independently verify how quickly we spotted this outage"? (For what it's worth, for the alert component you can do it yourself for free by subscribing to individual status pages (assuming they have the option) to the email-to-Slack integration.)
- wglb 7y agoI see only two references. Do you see more than that?