Rewindex

Companiesv0Incidents

v0: Degraded Builds

MinorStatus: resolvedStarted Resolved (26 min)1 updatewww.vercel-status.com (opens in new tab)
Part of an outage event

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

v0’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +11 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

blamed Auth0same windowCloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely, VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minv0 (this incident)posted +11 min
blamed Auth0same windowCloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely,VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minv0 (this incident)posted +11 min
v0 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["v0 (this incident)<br/>posted +11 min"]:::me
  root -.->|"same window"| 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

    This incident has been resolved.

From v0’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 www.vercel-status.com (opens in new tab).

v0 profileRecent v0 incidentsMarkdownJSON