Rewindex

RewindexOutage eventsJun 2, 2019

Google Cloud outage, Jun 2, 2019

8 vendors posted 8 incidents between 18:00 and 21:00 UTC, against about 2 incidents from 2 vendors in the same hours on an ordinary week. 3 vendors named Google Cloud in 3 incidents (3 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.

    7. first vendor named Google Cloud 18:45
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 hour1 vendor, 1 blamed Google CloudPendo1 to 4 hours later2 vendors, 2 blamed Google Cloudnpm, Confluent
Google Cloudown incident not archivedWithin an hour1 vendor, 1 blamed GoogleCloudPendo1 to 4 hours later2 vendors, 2 blamed GoogleCloudnpm, Confluent
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/>1 vendor, 1 blamed Google Cloud<br/>Pendo"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Google Cloud<br/>npm, Confluent"]:::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

1 vendor

  • +0 min

    Blames Google Cloud

    Incident, no impact listed

    PendoApplication outage

    …Application outage The issue with Google Cloud Platform has been resolved. Event processing has been caught up for the affected time period.…

1 to 4 hours later

2 vendors

  • +1 h 4 min

    Blames Google Cloud

    Major incident

    npmnpm Enterprise partial outage due to Google Compute Engine

    …npm Enterprise partial outage due to Google Compute Engine This incident has been resolved.…

  • +1 h 14 min

    Blames Google Cloud

    Incident, no impact listed

    ConfluentGoogle Platform Network Issues

    …Google Platform Network Issues Network issues affecting Confluent customers on GCP have been mitigated. Please see the Google Cloud support ticket for details: https://status.cloud.google.com/incident…

Same window, did not name anyone

5 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 2 in these hours).

Show all 5

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