6 ms·

What do you mean by this? The Google outage is a widespread outage of most GCP services.

by devmor 1y ago

pageandrew 1y ago
Google is claiming the root cause is with some of their central IAM services, which would have a cascading effect to the rest of their services.
- devmor 1y ago
  Where did you see this information? Was it on a social media channel? I do see the IAM services in the list of affected services in the incident report.
  - tom1337 1y ago
    check https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1S... > Multiple GCP products are experiencing impact due to Identity and Access Management Service Issue
  - ikiris 1y ago
    Scroll up. Its literally in this HN comment section highly upvoted.
    - devmor 1y ago
      It was not when I posted the reply that you are replying to 2 hours after I posted it.
ikiris 1y ago
The comment was self explanatory, and no, it wasn't a widespread GCP outage. Most everything was up except for GCS and firebase, and later on identity stuff started causing cascading issues but not when this was posted.
- zerd 1y ago
  > it wasn't a widespread GCP outage. If this wasn't widespread, what is? Incident affecting API Gateway, Agent Assist, AlloyDB for PostgreSQL, Apigee, Apigee Edge Private Cloud, Apigee Edge Public Cloud, Apigee Hybrid, Cloud Data Fusion, Cloud Firestore, Cloud Logging, Cloud Memorystore, Cloud Monitoring, Cloud Run, Cloud Security Command Center, Cloud Shell, Cloud Spanner, Cloud Workstations, Contact Center AI Platform, Contact Center Insights, Data Catalog, Database Migration Service, Dataform, Dataplex, Dataproc Metastore, Datastream, Dialogflow CX, Dialogflow ES, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Console, Google Cloud DNS, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Identity Platform, Identity and Access Management, Looker Studio, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Persistent Disk, Personalized Service Health, Pub/Sub Lite, Speech-to-Text, Text-to-Speech, Vertex AI Search
  - ikiris 1y ago
    Our entire infra in GCP stayed up just fine, we just couldn't manage anything. IDK what to tell you. Many of the things you list here were not down at all.
    - mirashii 1y ago
      That it wasn’t down for you does not mean it wasn’t down for others or even almost everyone. Certainly, Google wouldn’t have listed the services as having an outage if nobody was impacted. You can’t extrapolate from “works for me” to “it must have been working for everyone”.
      - ikiris 1y ago
        Dude, I literally was an SRE there. I'm well aware of how this stuff works. If some of those things listed had actual widespread outages, it would have been much much worse.

What do you mean by this? The Google outage is a widespread outage of most GCP services.

by devmor 1y ago

What do you mean by this? The Google outage is a widespread outage of most GCP services.

Google is claiming the root cause is with some of their central IAM services, which would have a cascading effect to the rest of their services.

devmor 1y ago
Where did you see this information? Was it on a social media channel? I do see the IAM services in the list of affected services in the incident report.
- tom1337 1y ago
  check https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1S... > Multiple GCP products are experiencing impact due to Identity and Access Management Service Issue
- ikiris 1y ago
  Scroll up. Its literally in this HN comment section highly upvoted.
  - devmor 1y ago
    It was not when I posted the reply that you are replying to 2 hours after I posted it.

ikiris 1y ago

The comment was self explanatory, and no, it wasn't a widespread GCP outage. Most everything was up except for GCS and firebase, and later on identity stuff started causing cascading issues but not when this was posted.

zerd 1y ago
> it wasn't a widespread GCP outage. If this wasn't widespread, what is? Incident affecting API Gateway, Agent Assist, AlloyDB for PostgreSQL, Apigee, Apigee Edge Private Cloud, Apigee Edge Public Cloud, Apigee Hybrid, Cloud Data Fusion, Cloud Firestore, Cloud Logging, Cloud Memorystore, Cloud Monitoring, Cloud Run, Cloud Security Command Center, Cloud Shell, Cloud Spanner, Cloud Workstations, Contact Center AI Platform, Contact Center Insights, Data Catalog, Database Migration Service, Dataform, Dataplex, Dataproc Metastore, Datastream, Dialogflow CX, Dialogflow ES, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Console, Google Cloud DNS, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Identity Platform, Identity and Access Management, Looker Studio, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Persistent Disk, Personalized Service Health, Pub/Sub Lite, Speech-to-Text, Text-to-Speech, Vertex AI Search
- ikiris 1y ago
  Our entire infra in GCP stayed up just fine, we just couldn't manage anything. IDK what to tell you. Many of the things you list here were not down at all.
  - mirashii 1y ago
    That it wasn’t down for you does not mean it wasn’t down for others or even almost everyone. Certainly, Google wouldn’t have listed the services as having an outage if nobody was impacted. You can’t extrapolate from “works for me” to “it must have been working for everyone”.
    - ikiris 1y ago
      Dude, I literally was an SRE there. I'm well aware of how this stuff works. If some of those things listed had actual widespread outages, it would have been much much worse.