Re:Google Cloud Networking Incident Postmortem
by sbr464 on Thursday June 06, 2019 @07:45PM
(#20120333)
I agree, but it’s pretty standard SLA verbiage (from the telco/bandwith provider days) to require the customer to request/register the SLA violation to benefit.
[ Parent
| on HN ]
Re:Google Cloud Networking Incident Postmortem
by vageli on Thursday June 06, 2019 @08:09PM
(#20120463)
> I agree, but it’s pretty standard SLA verbiage (from the telco/bandwith provider days) to require the customer to request/register the SLA violation to benefit.
FiOS has proactively given me per-day refunds of service without notification on my part. Weird to me that Verizon acts better than Google in this case.
Re:Google Cloud Networking Incident Postmortem
by macintux on Thursday June 06, 2019 @09:35PM
(#20120885)
It’s easier to determine “this line was down thus everyone along the line was also down” than what Google is facing.
Re:Google Cloud Networking Incident Postmortem
by vageli on Sunday June 09, 2019 @12:07AM
(#20137056)
Google knows the affected regions and probably has very fine grained data around this. I mean, they can even tell you metrics about your instances, they don't have monitoring on their own infrastructure to determine impact radius?
Re:Google Cloud Networking Incident Postmortem
by macintux on Sunday June 09, 2019 @09:57AM
(#20139207)
It’s a vastly complex problem. What servers were impacted? For what percentage of the overall outage was each server impacted? During that time, was the server offline or simply slower than usual?
And the part that even Google can’t know, even if they somehow can assemble all of the above: did it matter? Not all servers are created equal.
Small wonder they’re letting customers drive their own reimbursement process.