v0 (Vercel) · 121d ago
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
ResolvedYes — v0 had a problem on June 14, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved.”
Timeline
Started: 6/14/2026, 9:03:53 PM
Last update: 6/15/2026, 1:24:24 AM
Resolved: 6/15/2026, 1:24:24 AM
Affected: zwrthypbz06f
Updates
resolved
This incident has been resolved.
6/15/2026, 1:24:24 AM
monitoring
All traffic has been restored to the FRA1 Vercel Region.
6/15/2026, 12:25:30 AM
identified
The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.
6/14/2026, 11:15:26 PM
identified
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
6/14/2026, 9:26:03 PM
identified
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
6/14/2026, 9:07:51 PM
investigating
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
6/14/2026, 9:03:53 PM
More v0 (Vercel) incidents
- Increased build and deployment failures — resolved, 1d ago
- Delays in Drains, Observability, and Workflow in Washington (iad1) — resolved, 4d ago
- Vercel Auth login failures for pages with Deployment Protection enabled — resolved, 7d ago
- Elevated Sandbox error rates in Paris (cdg1) — resolved, 7d ago
- Build failures and 500 errors for functions using Edge runtime — resolved, 15d ago
- Deployment stuck in initializing state — resolved, 25d ago