Increased build and deployment failures
This incident has been resolved.
The latest update from Vercel.
State
Resolved
Started
20 d ago
2026-10-12 13:35 UTC
Lasted
6 h 36 min
until 2026-10-12 20:11 UTC
Worst impact
Partial outage
Timeline
7 updatesInvestigating
34 min 9%
Identified
5 h 48 min 88%
Monitoring
14 min 4%
Updates
Times in UTCAs posted by Vercel
This incident has been resolved.
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.
We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
We have identified the issue and are working on a fix. We will provide additional updates as they become available.
We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.
Affected components
4Vercel in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
17
Median duration
53 min
This incident
7.5× 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·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.
Vercel·Build failures and 500 errors for functions using Edge runtime
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