New Multi-region uptime checks and custom-domain status pages

Vercel Outage History

Daily provider-status observations and published incident history for Vercel.

Operational

Vercel is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Vercel for future changes.

84.2% of 57 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 86.7% 30 4

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Increased build and deployment failures
major Observed active window 6h 40m

View incident details and source

Started:

Builds Git Integrations
monitoring
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
identified
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.
identified
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.
identified
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.
identified
We have identified the issue and are working on a fix. We will provide additional updates as they become available.
investigating
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.
Delays in Drains, Observability, and Workflow in Washington (iad1)
major Observed active window 1h 24m

View incident details and source

Started:

Drains Logs Observability Queues Workflow
monitoring
Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available.
identified
A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.
investigating
We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.
Vercel Auth login failures for pages with Deployment Protection enabled
major Observed active window 1h 14m

View incident details and source

Started:

Routing Middleware
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating an issue causing Vercel Auth login failures for pages with Deployment Protection enabled. We will provide an update as more information becomes available.
Elevated Sandbox error rates in Paris (cdg1)
minor Observed active window 27m

View incident details and source

Started:

Sandbox
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.
identified
We've identified an issue where some customers may experience elevated error rates with Sandbox in Paris, France (cdg1). We are currently investigating this issue. We will share updates as they become available.
September 2026
Build failures and 500 errors for functions using Edge runtime
minor Observed active window 30m

View incident details and source

Started:

Builds
monitoring
A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.
Deployment stuck in initializing state
minor Observed active window 58m

View incident details and source

Started:

Builds
monitoring
We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.
investigating
We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.
Elevated Errors Triggering Deployments
major Observed active window 52m

View incident details and source

Started:

Builds
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.
investigating
We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.
Elevated error rate on Connect and Passport
major Observed active window 1h 37m

View incident details and source

Started:

identified
The issue has been identified and a fix is being implemented.
investigating
We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.
Elevated latency in VCR, Blob, and Sandbox API
minor Observed active window 1h 18m

View incident details and source

Started:

Blob Sandbox
monitoring
Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.
monitoring
The fix has been rolled out and we are seeing signs of recovery.
identified
The fix is currently being rolled out. We'll provide another update once the rollout is complete and we're beginning to see signs of recovery.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.
Increased deployment failures
major Observed active window 1h 0m

View incident details and source

Started:

Builds
monitoring
We are continuing to monitor for any further issues.
monitoring
We are seeing recovery in Builds and are continuing to monitor.
identified
We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available.
investigating
We are actively working to fix an issue causing some deployments that use IAD1 Function regions or Routing Middleware to fail. We will provide additional updates as they become available.
investigating
We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.

Legacy Incident Archive

61 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

March 2026
Dubai region (dxb1) is unavailable and traffic is being re-routed
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available.
identified
Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatic...
Get alerts for Vercel Subscribe to the provider incident feed Browse all services