[perlgeek]

Maybe you could encourage your colleagues to host the status page outside of AWS?

[hayleox]

We'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.

[koolba]

This 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.

[ckozlowski]

S3 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.

[all_usernames]

Possibly AWS status page wisely relied on a third party, which relied on a fourth party, which relied on S3.

[idlewords]

It took them ~30 minutes.

[LunaSea]

It took them 2 hours actually.

[johansch]

Maybe with GCP? :)

[apapli]

I'm happy to offer up some spare space on my godaddy hosted Linux plan if that helps...