6 ms·
> For most Google users there was little or no visible change to their services—search queries might have been a fraction of a second slower than usual for a fe
by jsiepkes 7y ago
> For most Google users there was little or no visible change to their services—search queries might have been a fraction of a second slower than usual for a few minutes but soon returned to normal, their Gmail continued to operate without a hiccup, and so on.
Google probably forgot that some of their own brands are also hosted on their cloud. Like Nest. Basically Nest was down entirely.
- jsiepkes 7y agoOk forget the above; coworker pointed out I missed the paragraph below....new rule; only post after 2 coffee in the morning.
- altmind 7y agoMost importantly, commerical gsuite was down. Its paid service(with bad, but still a SLA), and some companies worked on sunday. Pretty bad when both corp email and hangouts dont work - no way to communicate remediation steps.
- macintux 7y agoGood takeaway: don’t use the same communications provider for all of your collaboration needs. However figuring out, for example, whether Slack has a critical dependency on your provider may not be trivial.
- trollied 7y agoNot everywhere has Saturday/Sunday weekends, so many people work on Sundays. See https://en.wikipedia.org/wiki/Workweek_and_weekend#Around_the_world https://en.wikipedia.org/wiki/Workweek_and_weekend#Around_th...
- ben_jones 7y agoGitHub hooks for google cloud builder were also down, meaning if you chose google for deployment automation you were SOL. It wasn’t shown as down under any of the status pages, but it was definitely down for us. I get that outages happen. But having a dishonest status page just plain sucks.
- SquareWheel 7y agoMaybe the server was responding with a 200, but something deeper in the service just wasn't working. I expect these things are complicated and a status page is just an approximation.