Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
Jun 14, 21:03 UTCJun 15, 01:24 UTC
Duration
4h 21m
Impact
Major
Root cause
Not disclosed
Vercel, 90 days
32 incidents
Affected
FRA1 - Frankfurt, Germany, EuropeCDN - FRA1 - Frankfurt, Germany, Europe
Final update
This incident has been resolved.
Timeline
- Resolved · Jun 15, 01:24 UTC
This incident has been resolved.
- Monitoring · Jun 15, 00:25 UTC
All traffic has been restored to the FRA1 Vercel Region.
- Identified · Jun 14, 23:15 UTC
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 · Jun 14, 21:26 UTC
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- Identified · Jun 14, 21:07 UTC
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
- Investigating · Jun 14, 21:03 UTC
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
More from Vercel
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1821:36 UTC | Deployment stuck in initializing state | minor | 55m |
| Sep 1820:32 UTC | Elevated Errors Triggering Deployments | major | 50m |
| Sep 1815:14 UTC | Elevated Vercel KMS and Connect Errors | none | 0m |
| Sep 1707:11 UTC | Failures delivering Logs to Drains | none | 0m |
| Sep 1616:58 UTC | Missing Web Analytics and Speed Insights data | minor | 0m |
| Sep 1603:21 UTC | Invoice Generation Paused | none | 0m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.