Delays in observability data
Vercel reports a partial outage in AI Gateway, Observability, Queues, and Workflow. Observability and billing data is delayed, and the Workflows dashboard can show a run as pending after it started or finished. Vercel implemented a fix and is monitoring the recovery.
State
Monitoring
Started
Ongoing for
2 h 12 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
16 min 12%
Identified
33 min 25%
Monitoring
1 h 24 min 63%
Updates
Times in UTCAs posted by Vercel
A fix has been implemented, and recovery is in process. We are monitoring the results and will provide additional updates as we have them.
The issue has been identified and a fix is being implemented.
We are investigating an issue where observability and billing data is delayed. Run status on the Workflows dashboard on Vercel may be reported as “pending” even though the run may have already started or finished. Observability data on the AI Gateway dashboard is delayed and users may see low traffic. We will provide additional updates as we have them.
The issue has been identified and a fix is being implemented.
We are investigating an issue where observability and billing data is delayed. Run status on the Workflows dashboard on Vercel may be reported as “pending” even though the run may have already started or finished. Observability data on the AI Gateway dashboard is delayed and users may see low traffic. We will provide additional updates as we have them.
Affected components
5Vercel in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
16
Median duration
50 min
This incident
2.7× the median
Other Vercel incidents
All incidentsVercel·Elevated Sandbox and Blob request latency and errors
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.
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.
Vercel·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.
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.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.
https://outages.live/feed.xml?providers=vercel/feed subscribe https://outages.live/feed.xml?providers=vercelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane