v0: Elevated API and Dashboard Error Rates
Part of an outage event
Azure outage, Apr 1, 2021 · 13 vendors, 13 incidents
v0’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +6 min vs the first vendor naming Azure)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 3 blamed Azure<br/>LaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrog"]:::blames
root --> h1
me["v0 (this incident)<br/>posted +6 min"]:::me
root -.->|"same window"| meFull 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
- resolved
All systems normal.
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).