Rewindex

RewindexOutage eventsNov 16, 2021

Google Cloud outage, Nov 16, 2021

24 vendors posted 25 incidents between 17:00 and 22:00 UTC, against about 9 incidents from 8 vendors in the same hours on an ordinary week. 7 vendors named Google Cloud in 8 incidents (6 of them blamed it). Vendors reported a Google Cloud outage; Google Cloud’s own incident for this date is not in the archive.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when the first vendor named Google Cloud.

  1. first vendor named Google Cloud 17:30
Named Google CloudNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Google Cloud, grouped by when they posted, and vendors that blamed one of the vendors Google Cloud took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Google Cloudown incident not archivedWithin an hour6 vendors, 4 blamed Google CloudSegment, Bugsnag, Twingate, Sigma Computing +21 to 4 hours later2 vendors, 2 blamed Google CloudSmartsheet, Grafana Cloud
Google Cloudown incident not archivedWithin an hour6 vendors, 4 blamed GoogleCloudSegment, Bugsnag, Twingate,Sigma Computing +21 to 4 hours later2 vendors, 2 blamed GoogleCloudSmartsheet, Grafana Cloud
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Google Cloud<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>6 vendors, 4 blamed Google Cloud<br/>Segment, Bugsnag, Twingate, Sigma Computing +2"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Google Cloud<br/>Smartsheet, Grafana Cloud"]:::blames
  root --> h4

Vendors that named Google Cloud

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

6 vendors

  • +0 min

    Blames Google Cloud

    Incident, no impact listed

    SegmentData Delivery impacted by Google Cloud Platform outage

    …Data Delivery impacted by Google Cloud Platform outage An issue affecting Google Cloud Platform prevented Segment from delivering and retrying some events to Customer.io, Indicative, Kochava, Satismet…

  • +13 min

    Blames Google Cloud

    Critical incident

    BugsnagMajor outage across all Bugsnag services

    …d so some events may still be visible during that period. The incident was caused by this Google Cloud Networking issue: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh…

  • +24 min

    Blames Google Cloud

    Critical incident

    TwingateService provider networking outage

    …onnect their Connectors in order to restore access to protected resources. **Root cause** Google Cloud Platform \(GCP\) deployed a configuration change in their infrastructure that caused all requests…

  • +27 min

    Names Google Cloud

    Critical incident

    Sigma ComputingSigma services hosted on GCP are unreachable

    …Sigma services hosted on GCP are unreachable This incident has been resolved.…

  • +28 min

    Blames Google Cloud

    Major incident

    GorgiasNetworking error

    …Networking error The issue with Google Cloud Networking has been resolved as of Tuesday, 2021-11-16 11:28 US/Pacific. More information about the incident on their status page: https://status.cloud.goo…

  • +45 min

    Names Google Cloud

    Minor incident

    Grafana CloudHTTP 404 on GCP Hosted Stacks

    …HTTP 404 on GCP Hosted Stacks This incident has been resolved.…

1 to 4 hours later

2 vendors

Same window, did not name anyone

17 incidents started during the event without naming Google Cloud or another vendor. Some are part of it, some are a normal day’s background (about 9 in these hours).

Show all 17

Detected automatically from 21 status pages opening incidents in the peak hour (normally at most 5). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.