Rewindex

RewindexOutage eventsDec 14, 2020

Google Cloud outage, Dec 14, 2020

10 vendors posted 12 incidents between 12:00 and 13:00 UTC, against about 1 incidents from 1 vendors in the same hours on an ordinary week. 2 vendors named Google Cloud in 4 incidents (1 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.

    3. first vendor named Google Cloud 12:14
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 hour2 vendors, 1 blamed Google CloudSnowflake, Bugsnag
Google Cloudown incident not archivedWithin an hour2 vendors, 1 blamed GoogleCloudSnowflake, Bugsnag
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/>2 vendors, 1 blamed Google Cloud<br/>Snowflake, Bugsnag"]:::blames
  root --> h1

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

4 vendors

  • +0 min

    Names Google Cloud

    Major incident

    SnowflakeGCP - Europe (West-4): SI-20201214

    …GCP - Europe (West-4): SI-20201214 The Service Incident is now closed. A Root Cause Analysis (RCA) will be posted within the next 10 business days. We apologize for the inconvenience caused by this in…

  • +1 min

    Names Google Cloud

    Major incident

    SnowflakeGCP - US (Central 1): SI-20201214

    …GCP - US (Central 1): SI-20201214 The Service Incident is now closed. A Root Cause Analysis (RCA) will be posted within the next 10 business days. We apologize for the inconvenience caused by this inc…

  • +1 min

    Names Google Cloud

    Major incident

    SnowflakeGCP - Europe (West-2): SI-20201214

    …GCP - Europe (West-2): SI-20201214 The Service Incident is now closed. A Root Cause Analysis (RCA) will be posted within the next 10 business days. We apologize for the inconvenience caused by this in…

  • +20 min

    Blames Google Cloud

    Incident, no impact listed

    BugsnagBugsnag affected by Google Cloud Platform issues

    …Bugsnag affected by Google Cloud Platform issues The Google Cloud Platform issues which were impacting Bugsnag appear to be resolved. Symbolication of stack traces on new events is now working again,…

Same window, did not name anyone

8 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 1 in these hours).

Show all 8

Detected automatically from 15 status pages opening incidents in the peak hour (normally at most 4). 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.