Rewindex

CompaniesLogz.ioIncidents

Logz.io: Disruptions on app login

MinorStatus: resolvedStarted Resolved (5.0 h)1 updatestatus.logz.io (opens in new tab)
Part of an outage event

Auth0 outage, Apr 20, 2021 · 12 vendors, 12 incidents

Logz.io’s incident blames Auth0 as the cause. (hop 1, posted +1 min vs the first vendor naming Auth0)

“…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…”

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 Auth0LeverLogz.io (this incident)posted +1 min
Auth0own incident not archivedWithin an hour3 vendors, 3 blamed Auth0Wiz, Logz.io, Firebolt1 to 4 hours later1 vendor, 1 blamed Auth0LeverLogz.io (this incident)posted +1 min
Logz.io is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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
  me["Logz.io (this incident)<br/>posted +1 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Our monitoring systems have been clear regarding the login 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 resolved, and we believe this incident is over for us and our customers. We are aware of the importance of this service, and apologize for the inconvenience this has caused.

From Logz.io’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.logz.io (opens in new tab).

Logz.io profileRecent Logz.io incidentsMarkdownJSON