5 ms·
Not sure if this is my own personal bias, but I could have sworn this issue was effecting traffic for longer. My company wasn’t effected, so I wasn’t paying cl
by chairmanwow1 5y ago
Not sure if this is my own personal bias, but I could have sworn this issue was effecting traffic for longer.
My company wasn’t effected, so I wasn’t paying close attention to it. I was surprised to read it was only ~90 min that services were unreachable.
Anyone else have stabilizing ancedata?
- roytries 5y agoMaybe you're thinking of this incident? https://status.cloud.google.com/incidents/1xkAB1KmLrh5g3v9ZEZ7 https://status.cloud.google.com/incidents/1xkAB1KmLrh5g3v9ZE.... It was a few days earlier and took almost 2 hours.
- leetrout 5y agoIt was definitely more than 404's they are claiming. Go playground was 503'd.
- detaro 5y agoWhich it could easily have been because it itself received a 404 from something and couldn't handle that.
- cajones314 5y agoWe received errors at least 45 minutes before their stated time. :-/
- lrem 5y agoThen you have been hit by some other issue.
- lrem 5y agoAs a Googler privy to the internal postmortem: as stated in the public postmortem, all traffic was unaffected within 33 minutes of the problem appearing. The bug was very on/off: at 09:35PT a corrupted configuration stopped ~immediately (usually double digit seconds of propagation delay) all traffic. At 10:08PT it was verified that the whole service is running the configuration from before the corruption. The >1h duration was for inability to change your load balancing configuration.