News for hackers. Stuff that matters.
Re:DNS Outage at DigitalOcean by Rezo on Thursday March 24, 2016 @12:29PM (#11354156)
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.
Re:DNS Outage at DigitalOcean by dsr_ on Thursday March 24, 2016 @12:56PM (#11354402)
And don't use statuspage.io if your host is AWS, because theirs is too.
Re:DNS Outage at DigitalOcean by Rezo on Thursday March 24, 2016 @01:08PM (#11354500)
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.
Re:DNS Outage at DigitalOcean by TheSwordsman on Thursday March 24, 2016 @01:06PM (#11354486)
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.