Vercel
Vercel AI
No data
Last success —
No component payload
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
7 up0 degraded0 down0 unknown
Snapshot 08:41:05 UTC
updates every 60s
Official incident · Vercel AI
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
resolved · 2026-06-14 21:03:53 UTC · Resolved 2026-06-15 01:24:24 UTC
Duration 4h 20mOfficial title mentions toolmajor
Official updates
- resolved
This incident has been resolved.
- monitoring
All traffic has been restored to the FRA1 Vercel Region.
- 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.
- identified
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- identified
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- investigating
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
- status.claude.com/api/v2/summary.json
- status.openai.com/api/v2/summary.json + components.json
- status.x.ai/api/compat/summary.json (Cursor)
- status.x.ai/feed.xml (Grok)
- www.githubstatus.com/api/v2/summary.json
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.