outages.live
Live
VercelIncident ·

Elevated Sandbox and Blob request latency and errors

ResolvedOfficial update
0

On November 10, 2026, between 19:16 and 19:34 UTC, some Sandbox and Blob API requests in iad1 region experienced elevated latency and errors. A fix was applied, restoring service at 19:34 UTC and preventing this issue from recurring. This incident lasted 18 minutes and is being reported retroactively. We apologize for the disruption.

The latest update from Vercel.

State

Resolved

Started

Lasted

1 min

Worst impact

Partial outage

Timeline

1 update
21:0421:0421:0421:0521:05
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Vercel

Resolved

On November 10, 2026, between 19:16 and 19:34 UTC, some Sandbox and Blob API requests in iad1 region experienced elevated latency and errors. A fix was applied, restoring service at 19:34 UTC and preventing this issue from recurring. This incident lasted 18 minutes and is being reported retroactively. We apologize for the disruption.

Affected components

3
BlobSandboxStorage - Blob

Vercel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

21

Days with an incident

18

Median duration

47 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 55 min
median 47 min
90 days agoToday

Other Vercel incidents

All incidents

Vercel·Build delays and degraded Vercel Dashboard performance

Vercel reports delayed builds and slow or failed actions in the Vercel Dashboard. The affected components are Dashboard, Builds, Build & Deploy - Builds, and Dashboard - Dashboard. Vercel resolved the incident after 25 minutes and cleared the build backlog.

Resolved

Vercel·Delays in Logs and Observability data

The issue causing delays in Logs and Observability data has been resolved.

Resolved

Vercel·Increased build and deployment failures

This incident has been resolved.

Resolved

Vercel·Delays in Drains, Observability, and Workflow in Washington (iad1)

All services have recovered.

Resolved

Vercel·Vercel Auth login failures for pages with Deployment Protection enabled

This incident has been resolved.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=vercel
Slack
/feed subscribe https://outages.live/feed.xml?providers=vercel

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane