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
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 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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)
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
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.
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
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.
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.
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 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.
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.
June 2026
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
All traffic has been restored to the FRA1 Vercel Region.
identified
The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.
identified
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
identified
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
investigating
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
Elevated Build Errors for Secure Compute/Static IPs Projects
majorSource not attested
Last archived state: resolved
View archived record details
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 currently investigating this issue.
Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.
If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.
identified
The issue has been identified and a fix is being implemented.
A small number of requests may have seen elevated error rates in function invocations during this period.
Elevated Errors Creating New Deployments
minorSource not attested
Last archived state: resolved
View archived record details
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 reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
May 2026
Elevated Function Invocation Errors in Stockholm region (ARN1)
minorSource not attested
Last archived state: resolved
View archived record details
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've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
Elevated Errors on Vercel Dashboard (Project Overview Page)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
Delays Loading Runtime Logs
minorSource not attested
Last archived state: resolved
View archived record details
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 currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and are working closely with GitHub to resolve it.
investigating
We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.
investigating
We are continuing to investigate this issue.
investigating
We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs.
CLI deployments are unaffected at this time.
investigating
We are currently investigating this issue.
Elevated Build Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation was successfully rolled out, and builds are stable.
identified
The root cause has been identified and we are rolling out a mitigation.
identified
We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.
Missing Build CPU Minutes Usage Data
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
