Re:Netlify Status – build pipeline down for past 4 hours
by moocowtruck on Friday November 01, 2019 @11:23AM
(#21419765)
i 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
Re:Netlify Status – build pipeline down for past 4 hours
by jgalt212 on Friday November 01, 2019 @12:53PM
(#21420958)
True, 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.
Re:Netlify Status – build pipeline down for past 4 hours
by sunasra on Friday November 01, 2019 @11:55AM
(#21420146)
Exactly for this, I have built https://IncidentOK.com which sends alert over email/slack to user if any third party services like this reports an outage or incident.
Re:Netlify Status – build pipeline down for past 4 hours
by jaysh on Friday November 01, 2019 @12:21PM
(#21420510)
I 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.)
A region (or AZ for Amazon) is no more or less reliable then your run of the mill DC
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.)