3 ms·

I like how I found out about this here and not through an email. Tons of customer reports from our site of being logged out randomly (we use Firebase) and we ha

I like how I found out about this here and not through an email. Tons of customer reports from our site of being logged out randomly (we use Firebase) and we had no idea why.

deleted 7y ago
[deleted]
tlackemann 7y ago
The outage is going on for almost 12-hours. Quick math says that's 99.86% reliability. On top of this, they want to start charging $70/mo for GKE because they "[...] are also introducing a Service Level Agreement (SLA) that's financially backed with a guaranteed availability of 99.95%" (pulled from pricing[0]) This is unacceptable. [0] https://cloud.google.com/kubernetes-engine/pricing https://cloud.google.com/kubernetes-engine/pricing
- BilalBudhani 7y ago
  I'm guessing because we are going through a pandemic they might be taking more time than usual to apply fixes.
  - pm90 7y ago
    They’ve been pretty vocal about the fact that this has nothing to do with the pandemic.
    - quicklime 7y ago
      The outage itself might not have been caused by anything related to the pandemic, but the resolution is likely being done by engineers adjusting to working from home.
- 9nGQluzmnq3M 7y ago
  The current/remaining issue is "Affected customers may experience delayed IAM modifications that surface across multiple Google Cloud Platform services." In simple terms, user login/auth is working fine, it's just modifications (new service accounts, access changes, etc) that are delayed. Obviously not great, but this doesn't really affect the critical path of any systems that are already up and running.