[Rezo]

Their status page at https://status.digitalocean.com is also now giving an intermittent "500 Internal Server Error" nginx error, probably from the load. That's why you should use a service like https://www.statuspage.io for your important stuff, even though creating a status page is a fun side-project for a dev team.

[crisopolis]

So what you're saying is that instead of running their own Status Page on their own infrastructure that's reachable. They should outsource it to statuspage.io and pay another company to do it?

[Rezo]

Yes, that's pretty standard. Availability monitoring and status reporting should be external and separate from your own infrastructure, otherwise neither may be available when you need it the most.

[dsr_]

And don't use statuspage.io if your host is AWS, because theirs is too.

[Rezo]

They do have geo-region (not just AZ) redundancy and failover, which puts them quite a bit above most home-grown company status pages in my experience. But yes, if the problem was for example in R53 it would indeed be better to have an solution without that AWS dependency.

[TheSwordsman]

Eh, as I remember it they have stuff in multiple AWS regions. Would take a global AWS failure to bring them down. This was my justification for going with them while working somewhere that used AWS.

That said, while it is extremely unlikely it shouldn't be discounted as impossible.

[clentaminator]

But who monitors the status of statuspage.io?

[colinbartlett]

I know you're joking, but I do: Check out https://StatusGator.com. StatusPage.io has a status page at metastatuspage.com which my company monitors.

[ludbb]

And who monitors your company monitors? :)

[jessaustin]

Are you also on AWS? Apparently you're not on DO...