4 ms·
Maybe you could encourage your colleagues to host the status page outside of AWS?
by perlgeek 10y ago
Maybe you could encourage your colleagues to host the status page outside of AWS?
- johansch 10y agoMaybe with GCP? :)
- oxguy3 10y agoWe'll have to wait for the postmortem, but I bet it was an unintentional dependency on S3 that no one realized had come into place until S3 went down -- especially considering how fast they were able to remove the dependency and fix it.
- ckozlowski 10y agoS3 gets used to store a lot of static content. Can't speak for that team, but I'm sure they'll take that feedback. Happy the banner functionality remained unimpeded.
- idlewords 10y agoIt took them ~30 minutes.
- LunaSea 10y agoIt took them 2 hours actually.
- koolba 10y agoThis reminds me of a GitHub outage from them having a build dependency on GitHub. IIRC, they tried to roll back to building a prior version but since the site was offline, the build failed.
- all_usernames 10y agoPossibly AWS status page wisely relied on a third party, which relied on a fourth party, which relied on S3.
- apapli 10y agoI'm happy to offer up some spare space on my godaddy hosted Linux plan if that helps...