We use downdetector.com because status pages tend to take up to an hour or so to update, if they ever do.
reply
jgrahamc 4 days ago [-]
1042 UTC First alert of global traffic problem 1057 UTC Internal group chat room up and running 1102 UTC Status page updated
So, first alert to status page was 20 minutes.”””
In those 20m we had repeatedly checked your status page, realised it was our issue and started pulling engineers to deal with it as per procedure. People are on call, it's highly disruptive.
Surely you knew within those 20m that something was up?
In the end we realised it wasn't our issue because we checked Twitter.
Yep. I tend to agree that we could have gone faster. The difficulty is that getting clear information out fast when you are dealing with a difficult situation is hard.
But, I guess we could have put some status up quicker.
I'm irritated, however, that you picked on Cloudflare as a bad actor here when we strive to be transparent and quick to get out full information whereas others (e.g. Amazon) are slow as mud.
But I get that being on the other side of this is difficult when you don't have information.
Amazon, Google, seem far far worse. I wasn't intending for my post to me representative, just that the CF outage is recent and affects me more personally than the others atm. Also, I had zero expectation my comment would actually be read, this is quite a surprise.
If it's any incentive, if the status page had any inkling that something was wrong, I'd be first on here posting "omg their status page is real".
Fair enough. Thanks for making the comment. Made me think about how fast we act in terms of public status pages. And sorry that route leak affected you.
Also don't get me wrong, you do a great service. It's just a pet peeve that it seems invariably status pages are a lie.