v0: Degraded External API Calls and Edge Config usage
Timeline of updates
- resolved
The incident was resolved. During this window (11:14 - 15:16 UTC, depending on regions), some request data, like external API calls, was not recorded due to an internal logging disruption. As a result, requests made during this period will not appear in the dashboard, logs, or analytics APIs. Application execution was not impacted. The issue only affected the recording of observability and billing data.
From v0’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.vercel-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by v0, started 2025-07-03 14:36 UTC, resolved after 1.2 h, 1 update(s).
- Title
- Degraded External API Calls and Edge Config usage
- Vendor
- v0
- Date
- URL
- https://rewindex.com/company/v0/incidents/4dswlwtdrt8d
v0 profileRecent v0 incidentsAll outages on July 3, 2025v0 in July 2025MarkdownJSON