Elevated latency in VCR, Blob, and Sandbox API
Blob has fully recovered. This incident has been resolved.
The latest update from Vercel.
State
Resolved
Started
58 d ago
2026-09-04 19:11 UTC
Lasted
1 h 16 min
until 2026-09-04 20:27 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
21 min 28%
Identified
33 min 43%
Monitoring
22 min 29%
Updates
Times in UTCAs posted by Vercel
Blob has fully recovered. This incident has been resolved.
Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.
The fix has been rolled out and we are seeing signs of recovery.
The fix is currently being rolled out. We'll provide another update once the rollout is complete and we're beginning to see signs of recovery.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.
Affected components
3Vercel in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
17
Median duration
53 min
This incident
1.4× the median
Other Vercel incidents
All incidentsVercel·Delays in Logs and Observability data
The issue causing delays in Logs and Observability data has been resolved.
Vercel·Increased build and deployment failures
This incident has been resolved.
Vercel·Delays in Drains, Observability, and Workflow in Washington (iad1)
All services have recovered.
Vercel·Vercel Auth login failures for pages with Deployment Protection enabled
This incident has been resolved.
Vercel·Elevated Sandbox error rates in Paris (cdg1)
This incident has been resolved.
Follow Vercel
Your coding agent knows when Vercel is down, and tells you when a failure is theirs, not yours. You can also get Vercel incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "vercel" and tell me if Vercel has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=vercel/feed subscribe https://outages.cc/feed.xml?providers=vercelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane