4 ms·
It's crazy how much better the communication (including updates and status pages) is of the companies that rely on AWS than AWS' communication itself. https://
by tuna-piano 10y ago
It's crazy how much better the communication (including updates and status pages) is of the companies that rely on AWS than AWS' communication itself.
https://status.heroku.com/incidents/1059 https://status.heroku.com/incidents/1059
- busterarm 10y agoAlso, https://status.pantheon.io https://status.pantheon.io
- tcsf 10y agoBlake Gentry gave a full accounting of Heroku's response process here - http://www.heavybit.com/library/video/every-minute-counts-coordinating-herokus-incident-response/ http://www.heavybit.com/library/video/every-minute-counts-co... Amazon should take notes.
- all_usernames 10y agoI feel for them. Imagine, 40 or 50 different engineering teams all responsible for updating their statuses. At this moment on the AWS status page I see random usage of the red, yellow, and green icons, even though all the status updates are "Increased error rates." What that tells me is that there's no unified communication protocol across the teams, or they're not following it. And just imagine what it's like being on the S3 team right now. I notice even Cloudflare is starting to have problems serving up pages now.
- SnowingXIV 10y agoFont Awesome went out for me for a bit, but they did a great job getting back up and keeping their users in the loop. https://status.fortawesome.com/ https://status.fortawesome.com/