outages.live
Live
VercelIncident ·

Build delays and degraded Vercel Dashboard performance

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

25 min

Worst impact

Degraded

Timeline

3 updates
18:2518:3118:3718:4418:50
DegradedUpdate postedTimes in UTC

Investigating

11 min 45%

Monitoring

14 min 55%

Updates

Times in UTC

As posted by Vercel

Resolved

This incident has been resolved. The build backlog has been cleared.

Monitoring

We are seeing recovery after taking corrective action to address latency. We are continuing to process delayed builds. Vercel CI has also been affected. We will provide additional updates as they become available.

Investigating

We've identified an issue where some customers may experience delayed builds, slow page loads, and failed actions in the Vercel Dashboard. We are investigating the cause. We will provide additional updates as they become available.

Affected components

4
DashboardBuildsBuild & Deploy - BuildsDashboard - Dashboard

Vercel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

20

Days with an incident

17

Median duration

49 min

This incident

48% 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 49 min
90 days agoToday

Other Vercel incidents

All incidents

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

Vercel·Elevated Sandbox error rates in Paris (cdg1)

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