As of 8:06:07 AM PDT, all of my Firebase projects in us-central1 are back up.
We saw a complete silencing of our highly used Cloud Functions between 7:15 AM PDT and 7:38 AM PDT, but had reports from our users as early as 7:10 AM PDT.
My favorite part about https://status.cloud.google.com/incident/zall/20005 is that 7:49 AM PDT's update acknowledges that customers can't create support requests. Not like they'd do anything. Every time we've gone to GCP support, we've been unhappy with excessive back-and-forth, non-responsiveness on the part of the responsible parties, and generally extremely long durations between "we are completely down" and "everything would be fine had you not hacked around our incompetence three days ago".
Maybe this is a "grass is greener" sort of thing but I can't imagine AWS is this unreliable. This is the third major GCP outage we've had this year, and last time (not even three weeks ago!) it was three hours long.
> Every time we've gone to GCP support, we've been unhappy with excessive back-and-forth
Exactly this! I love GCP (especially firebase functions), inspite of these service disruptions. But, I can't deal with GCP support. They are unbelievably incompetent and have no understanding of the problem or solution. I feel like paying for support only to waste my time - explaining my problem to them with no hope for a solution.
>Really irritating that they never update the status pages automatically, or even in a timely manor
In my experience any real status page that matters is irrelevant as soon as the powers that be become aware of it and it becomes sort of non technical and politicized. To some extent that seems almost inevitable depending on the organization.
I worked at one place where "The guy who runs the twitter account." ran a status page. Not that he knew how to do anything (The one time I know he wanted to change the page he couldn't figure out how to do it.), but he was the only one allowed to approve / make updates. But it didn't matter as he wasn't on call, nobody was quite sure who that person was from day to day. He or she was in some marketing department and their idea of a sense of urgency was "sometime this week ... maybe".
To double-down on this, I wish companies more broadly would stop lying about their uptime on their status pages. It just creates chaos and confusion.
It also forces otherwise-honest companies to also lie about their uptime, because they don't want to be the one status page that actually shows all the little blips that naturally occur with an actively maintained product.
I wonder why they would choose not to automate updating the status page (because they 100% do automate having alarms for when things break) - maybe they think that, even with high error rates, it could be a false alarm or maybe a regional outage?
There is a broad Google Cloud outage since appx. 9am CST. Their status page is green but someone from Google acknowledged the issue on Twitter. The GCP slack is also abuzz with users reporting issues across many many services.
What is “Google Cloud Components”, sounds like something all the other products depend on. If that’s the case, a lot of other products should be marked as down in their status page, other users have confirmed a lot of products are down. This is really irritating.
For ~40 minutes, it was also impossible to SSH into any Compute Engine instance that uses OS Login for authentication, but it seems to have been resolved in the last few minutes.
[+] [-] djsweet|6 years ago|reply
We saw a complete silencing of our highly used Cloud Functions between 7:15 AM PDT and 7:38 AM PDT, but had reports from our users as early as 7:10 AM PDT.
My favorite part about https://status.cloud.google.com/incident/zall/20005 is that 7:49 AM PDT's update acknowledges that customers can't create support requests. Not like they'd do anything. Every time we've gone to GCP support, we've been unhappy with excessive back-and-forth, non-responsiveness on the part of the responsible parties, and generally extremely long durations between "we are completely down" and "everything would be fine had you not hacked around our incompetence three days ago".
Maybe this is a "grass is greener" sort of thing but I can't imagine AWS is this unreliable. This is the third major GCP outage we've had this year, and last time (not even three weeks ago!) it was three hours long.
[+] [-] QueensGambit|6 years ago|reply
Exactly this! I love GCP (especially firebase functions), inspite of these service disruptions. But, I can't deal with GCP support. They are unbelievably incompetent and have no understanding of the problem or solution. I feel like paying for support only to waste my time - explaining my problem to them with no hope for a solution.
[+] [-] samblr|6 years ago|reply
[+] [-] yeldarb|6 years ago|reply
All of our Firebase projects are missing from their console, deploys fail, auth fails, getting 404s for their libraries.
Seems intermittent at the moment. But spreading.
[+] [-] ssijak|6 years ago|reply
[+] [-] Nabi|6 years ago|reply
[+] [-] ehacke|6 years ago|reply
Really irritating that they never update the status pages automatically, or even in a timely manor. As if customers won't notice.
[+] [-] duxup|6 years ago|reply
In my experience any real status page that matters is irrelevant as soon as the powers that be become aware of it and it becomes sort of non technical and politicized. To some extent that seems almost inevitable depending on the organization.
I worked at one place where "The guy who runs the twitter account." ran a status page. Not that he knew how to do anything (The one time I know he wanted to change the page he couldn't figure out how to do it.), but he was the only one allowed to approve / make updates. But it didn't matter as he wasn't on call, nobody was quite sure who that person was from day to day. He or she was in some marketing department and their idea of a sense of urgency was "sometime this week ... maybe".
[+] [-] ehacke|6 years ago|reply
It also forces otherwise-honest companies to also lie about their uptime, because they don't want to be the one status page that actually shows all the little blips that naturally occur with an actively maintained product.
[+] [-] demosthenes14|6 years ago|reply
[+] [-] sciurus|6 years ago|reply
[+] [-] judge2020|6 years ago|reply
[+] [-] sdedovic|6 years ago|reply
[+] [-] bluehatbrit|6 years ago|reply
[+] [-] sillysaurusx|6 years ago|reply
[+] [-] bithavoc|6 years ago|reply
[+] [-] dijit|6 years ago|reply
[+] [-] kgraves|6 years ago|reply
https://news.ycombinator.com/item?id=22707876
This confirms my suspicions and my concerns still persist when choosing GCP
[+] [-] jtylr|6 years ago|reply
[+] [-] moon2|6 years ago|reply
The status page has been updated: https://status.cloud.google.com/
[+] [-] tomwas54|6 years ago|reply
[+] [-] _-___________-_|6 years ago|reply
[+] [-] r1ch|6 years ago|reply
[+] [-] bauerd|6 years ago|reply
GKE is working as normal in west-3c
[+] [-] aaronlifshin|6 years ago|reply
[+] [-] sandGorgon|6 years ago|reply
[+] [-] ohtangza|6 years ago|reply
[+] [-] zwily|6 years ago|reply