Rewindex

CompaniesSvixIncidents

Svix: Auth0 is down and it's causing the dashboard not to load (doesn't affect normal Svix operations)

MinorStatus: resolvedStarted Resolved (43 min)2 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Oct 30, 2023 · 24 vendors, 24 incidents

Svix’s incident is a second hop: it blames Auth0, which was affected by Cloudflare. (hop 2, posted +9 min vs the first vendor naming Cloudflare)

“…Auth0 is down and it's causing the dashboard not to load (doesn't affect normal Svix operations) This incident has been resolved. A fix has been implemented and we are monitoring the results. This inc…”

Swipe sideways to see the whole diagram.

blamed Auth0blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely, VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minSvix (this incident)posted +9 min
blamed Auth0blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely,VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minSvix (this incident)posted +9 min
Svix is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 3 blamed Cloudflare<br/>Census, Rootly, Optimizely, Vanta"]:::blames
  root --> h1
  p0["Auth0<br/>own incident not archived"]:::inferred
  root -.-> p0
  k0["Svix, Dremio<br/>+9 min to +39 min"]:::hop2
  p0 -->|"blamed Auth0"| k0
  me["Svix (this incident)<br/>posted +9 min"]:::me
  p0 -->|"blamed Auth0"| 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.

Affected components: Dashboard

Timeline of updates

  1. monitoring

    A fix has been implemented and we are monitoring the results.

  2. resolved

    This incident has been resolved.

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

Svix profileRecent Svix incidentsMarkdownJSON