Major incident
Vercel: Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
Jun 14, 2026, 21:03 UTC
started
01:24 UTC
resolved June 15, 2026
4 h 21 min
duration
Affected: FRA1 - Frankfurt, Germany, Europe
Current status of Vercel: Operational — live Vercel status
Timeline
- Jun 14, 2026, 21:03 UTCinvestigatingWe are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
- Jun 14, 2026, 21:07 UTCidentifiedWe are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- Jun 14, 2026, 21:26 UTCidentifiedThe impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- Jun 14, 2026, 23:15 UTCidentifiedThe 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.
- Jun 15, 2026, 00:25 UTCmonitoringAll traffic has been restored to the FRA1 Vercel Region.
- Jun 15, 2026, 01:24 UTCresolvedThis incident has been resolved.
Updates as published by Vercel (original).
More Vercel incidents
- October 23, 2026 Delays in Logs and Observability data
- October 12, 2026 Increased build and deployment failures
- October 10, 2026 Delays in Drains, Observability, and Workflow in Washington (iad1)
- October 6, 2026 Vercel Auth login failures for pages with Deployment Protection enabled
- October 6, 2026 Elevated Sandbox error rates in Paris (cdg1)
- September 28, 2026 Build failures and 500 errors for functions using Edge runtime