|
|
|
|
|
|
by djsweet
2255 days ago
|
|
|
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. |
|
|
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.