outages.live
Live

Vercel

Vercel is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

20

Days with an incident

17

Median duration

53 min

Longest incident

6 h 55 min

Components

59

Dashboard

Dashboard Operational
90 days ago2 days with an incidentToday
Support Center Operational
90 days agoNo incidentsToday
Support Chat Operational
90 days agoNo incidentsToday

Build & Deploy

Builds Operational
90 days ago6 days with an incidentToday
npm Registry Operational
90 days agoNo incidentsToday

CDN

ARN1 - Stockholm, Sweden Operational
90 days agoNo incidentsToday
BOM1 - Mumbai, India Operational
90 days agoNo incidentsToday
CDG1 - Paris, France, Europe Operational
90 days agoNo incidentsToday
CLE1 - Cleveland, East US Operational
90 days agoNo incidentsToday
CPT1 - Cape Town, South Africa Operational
90 days agoNo incidentsToday
DUB1 - Dublin, Ireland Operational
90 days agoNo incidentsToday
DXB1 - Dubai, UAE Operational
90 days agoNo incidentsToday
FRA1 - Frankfurt, Germany, Europe Operational
90 days agoNo incidentsToday
GRU1 - São Paulo, Brazil Operational
90 days agoNo incidentsToday
HKG1 - Hong Kong Operational
90 days agoNo incidentsToday
HND1 - Tokyo, Japan Operational
90 days agoNo incidentsToday
IAD1 - Washington DC, USA Operational
90 days agoNo incidentsToday
ICN1 - Seoul, South Korea Operational
90 days agoNo incidentsToday
KIX1 - Osaka, Japan Operational
90 days agoNo incidentsToday
LHR1 - London, UK Operational
90 days agoNo incidentsToday
PDX1 - Portland, West US Operational
90 days agoNo incidentsToday
SFO1 - San Francisco, CA, USA Operational
90 days agoNo incidentsToday
SIN1 - Singapore Operational
90 days agoNo incidentsToday
SYD1 - Sydney, Australia Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration1 h 2 min16:31 to 17:32Delays in Logs and Observability dataDegraded

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

Oct 12, 2026

Duration6 h 36 min13:35 to 20:11Increased build and deployment failuresPartial outage

This incident has been resolved.

Oct 10, 2026

Duration1 h 21 min00:15 to 01:37Delays in Drains, Observability, and Workflow in Washington (iad1)Partial outage

All services have recovered.

Oct 6, 2026

Duration16 min16:10 to 16:26Vercel Auth login failures for pages with Deployment Protection enabledPartial outage

This incident has been resolved.

Duration25 min09:12 to 09:36Elevated Sandbox error rates in Paris (cdg1)Degraded

This incident has been resolved.

Sep 28, 2026

Duration27 min13:44 to 14:11Build failures and 500 errors for functions using Edge runtimeDegraded

This incident has been resolved.

Sep 18, 2026

Duration55 min21:36 to 22:31Deployment stuck in initializing stateDegraded

This incident has been resolved.

Duration50 min20:32 to 21:22Elevated Errors Triggering DeploymentsPartial outage

The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.

Sep 17, 2026

Duration1 min07:11 to 07:11Failures delivering Logs to DrainsNotice

Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.

Sep 16, 2026

Duration1 min03:21 to 03:21Invoice Generation PausedNotice

Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.

Sep 10, 2026

Duration1 h 34 min17:42 to 19:16Elevated error rate on Connect and PassportPartial outage

Connect and Passport have fully recovered. This incident has been resolved.

Sep 4, 2026

Duration1 h 16 min19:11 to 20:27Elevated latency in VCR, Blob, and Sandbox APIDegraded

Blob has fully recovered. This incident has been resolved.

Sep 1, 2026

Duration59 min19:59 to 20:58Increased deployment failuresPartial outage

This incident has been resolved. Builds have recovered.

Aug 26, 2026

Duration1 h 22 min03:06 to 04:28Failures logging in with Vercel CLIPartial outage

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane