Rewindex

RewindexOutage eventsApr 20, 2021

Auth0 outage, Apr 20, 2021

12 vendors posted 12 incidents between 15:00 and 18:00 UTC, against about 5 incidents from 5 vendors in the same hours on an ordinary week. 4 vendors named Auth0 in 4 incidents (4 of them blamed it). Vendors reported an Auth0 outage; Auth0’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 Auth0.

    7. first vendor named Auth0 15:47
Named Auth0Named another vendorDid not name anyoneEach column is 30 minutes

How it spread

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

Swipe sideways to see the whole diagram.

Auth0own incident not archivedWithin an hour3 vendors, 3 blamed Auth0Wiz, Logz.io, Firebolt1 to 4 hours later1 vendor, 1 blamed Auth0Lever
Auth0own incident not archivedWithin an hour3 vendors, 3 blamed Auth0Wiz, Logz.io, Firebolt1 to 4 hours later1 vendor, 1 blamed Auth0Lever
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["Auth0<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed Auth0<br/>Wiz, Logz.io, Firebolt"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Auth0<br/>Lever"]:::blames
  root --> h4

Vendors that named Auth0

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

Within an hour

3 vendors

  • +0 min

    Blames Auth0

    Major incident

    WizIntermittent login issues - Auth0 is down

    …Intermittent login issues - Auth0 is down This incident has been resolved.…

  • +1 min

    Blames Auth0

    Minor incident

    Logz.ioDisruptions on app login

    …gin issue, and we have received positive indications from our customers as well, although Auth0 have not yet fully reported resolution on their end. Auth0 have been reporting most customers are resolv…

  • +38 min

    Blames Auth0

    Critical incident

    FireboltLogging into FIrebolt may fail

    …e are monitoring the results. The issue has been identified and is being caused due to an Auth0 outage. This incident has been resolved. We are currently investigating the issue. Log-in attempts can e…

1 to 4 hours later

1 vendor

  • +1 h 47 min

    Blames Auth0

    Major incident

    LeverIncreased error rate in Auth0

    …Increased error rate in Auth0 Auth0 has confirmed that the issue with error rates is resolved. More information on the incident can be found here https://status.auth0.com/incidents/zvjzyc7912g5?u=v0zz…

Same window, did not name anyone

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

Show all 8

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