Rewindex

RewindexOutage eventsJun 8, 2021

Fastly outage, Jun 8, 2021

27 vendors posted 26 incidents between 10:00 and 11:00 UTC, against about 2 incidents from 2 vendors in the same hours on an ordinary week. 2 vendors named Fastly in 2 incidents (2 of them blamed it). Vendors reported a Fastly outage; Fastly’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 Fastly.

    3. first vendor named Fastly 10:00
Named FastlyNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

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

Swipe sideways to see the whole diagram.

Fastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, Braze
Fastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, Braze
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["Fastly<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed Fastly<br/>RubyGems.org, Braze"]:::blames
  root --> h1

Vendors that named Fastly

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

Within an hour

2 vendors

  • +0 min

    Blames Fastly

    Major incident

    RubyGems.orgElevated Errors

    …levels and errors return to normal. The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj. This in…

  • +10 min

    Blames Fastly

    Major incident

    BrazeConnectivity issues due to Fastly CDN outage

    …Connectivity issues due to Fastly CDN outage Error rates returned to normal since the last update and this issue appears to be resolved.…

Same window, did not name anyone

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

Show all 24

Detected automatically from 32 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.