Earlier quoted context omitted.
It just updated. Maybe affected by their own outage!
Just proves how shady the status page and sla stuff is
or how difficult it actually is to do that type of thing at scale
GCP Outage
321–330 of 539 posts
Re: GCP Outage
#322What's crazy is that RCS messaging is down as a result of this outage. It shows how poorly the technology or infrastructure was designed.
[deleted]
Re: GCP Outage
#323Smells like BGP since there are services people claim have nothing to do with GCP being affected. OpenRouter is down, Lovable is down, etc.
AWS seems fine though. My bet is Cloudflare.
Re: GCP Outage
#324Well, good luck to all googlers dealing with this, that's not fun :(
Re: GCP Outage
#325Earlier quoted context omitted.
It is not the status page that drives customer compensation. It is downtime.
The status page is essentially an admission of guilt. It can require approval from the legal department and a high level official from the company to approve updating it and the verbiage used on the status page.
> It can require approval from the legal department and a high level official from the company to approve updating it and the verbiage used on the status page.
Is that true in this case or are you speculating? My company runs a cloud platform. Our strategy is to have outages happen as rarely as possible and to proactively offer rebates based on customer-measured downtime. I don't know why people would trust vendors that do otherwise.
Re: GCP Outage
#326Would be comedy if one of the progenitors of this took Sundar’s buyout offer yesterday and let the world burn today.
Re: GCP Outage
#327GPay which is a widely used payment service in India is down as well
India is having a really bad day today
Re: GCP Outage
#328> No major incidents … Proceeds to show worldwide degraded service level alerts.
Yep. Self-reporting status pages are pretty near worthless. At my former large company (not FAANG), we weren't allowed to update the status page until we got VP approval, which also required approval from both PR and Legal. It would take a lot more time and effort to get those approvals than to just fix the problem and move on.
SLA contracts, clawbacks, and performance obligations make these pages a bit of a minefield for CSPs. When I was at a top-tier CSP, we had the status page that was public, one that was for a trusted tier of customers, one built for a customer-by-customer basis, and one for internal engineering.
Re: GCP Outage
#329sheesh so many side-affected issues accross all systems, maybe big tech companies like google shouldn't have laid off all those engineers..
https://www.google.com/appsstatus/dashboard/incidents/Eab7zG...
but no tech bros, just keep following your ketamine addled edgelord when he did this with twitter..