News for hackers. Stuff that matters.
Re:Google Services Experiencing Disruptions by manigandham on Thursday September 24, 2020 @10:14PM (#24585919)
Properly investigating takes time. There are constant reports of something not working by customers so they need to confirm that it actually is internal and widespread first.

Also SLAs and service credits are tied to these official notices which causes even more delay before status updates are approved.

Re:Google Services Experiencing Disruptions by AnotherTechie on Friday September 25, 2020 @12:15AM (#24586520)
when soemthing this broadly painful happens at a company of Google's scale --typically you have something like a hundred people internally that all got paged.
Re:Google Services Experiencing Disruptions by gowld on Thursday September 24, 2020 @10:17PM (#24585939)
There's no reason for service credits to tied be to the dashboard and not to determinations made after the investigation is over.
Re:Google Services Experiencing Disruptions by manigandham on Friday September 25, 2020 @02:02AM (#24586997)
The SLA guarantees a certain level of no problems. The dashboard officially says there's a problem. This creates liability.
Re:Google Services Experiencing Disruptions by a012 on Thursday September 24, 2020 @10:20PM (#24585955)
They should have pro-active monitoring system and update status page automatically when it detected disruption. Especially when you account to it's extremely hard to get human supports from Google because they automated it.
Re:Google Services Experiencing Disruptions by mook on Thursday September 24, 2020 @10:50PM (#24586105)
I wouldn't be surprised if, at Google's scale, something or other is disrupted all the time.

I think I'd prefer a status page that reflected that, or even no status page at all with an explanation, rather than a lying one, though.

Re:Google Services Experiencing Disruptions by hknd on Friday September 25, 2020 @03:50AM (#24587577)
Google has multiple internal alerting systems and people are aware of any disruption/delay/anomaly from the minute it happens.

The on-caller for the specific service decides on how to produce.

The status dashboard is something which will be (manually, yes by hand) updated by an operations employee, who is a couple of layers behind the actual SWE/SRE who gets the page.