Comment by kjuulh
2 days ago
Something must be preventing them updating the status page at this point. Of course they could still deem it not enough, but just from my limited tests, docker, buf, etc (it may not be GCP that is down, but it is quite the coincidence). are outright down. I'd wager that this is much more widespread.
I'm actually on a bridge call with Google Cloud, we're a large customer -- I just learned today that their status page is not automated, instead someone actually manually updates it!
That's the case with every status page. These pages are managed by business people not engineers, because their primary purpose is to show customers that the company is meeting contractually defied SLAs.
Surelly no SLA will be based on the display of the status page...
3 replies →
This is actually the norm for status pages. If you look at the various status page offerings you'll see that they're designed around manual updates.
The best way to consistently having good "time to response" metrics, is to be the one deciding when an incident "actually" started happening, if at all :)
This feels very much like when facebook, locked themselves out of their datacenters. ;)
* https://www.datacenterdynamics.com/en/news/facebook-blames-m...
Except that AWS, CloudFlare and a bunch others are also down :-O
4 replies →
The bigger you are, the more you want a human involved in the decision to publicly declare an incident.
That's fairly typical. You want a human in the loop for decisions like that.
Most status pages are manual.
At least some of the information has to be.
The weird part is that it took them almost an full hour to update it.