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.
August 2026
New container functions are failing
majorSource not attested
Last archived state: resolved
View archived record details
Functions
monitoring
We have deployed a fix. Newly deployed container functions are working as expected.
identified
We've identified an issue where newly deployed container functions may return 5XX errors.
Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.
Logs unavailable to query in Dashboard
majorSource not attested
Last archived state: resolved
View archived record details
Logs
monitoring
We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.
investigating
We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.
Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard
Services have recovered. We are still working to ingest missing observability data during this period.
monitoring
Login with TOTP has completely recovered. We are still working to ingest missing observability data during this period. We will share more information as it becomes available.
monitoring
We are continuing to monitor for any further issues.
monitoring
We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available.
investigating
We are also investigating an issue where some customers may be unable to sign in to Dashboard with time-based one-time passwords (TOTP). We will share updates as they become available.
investigating
We are continuing to investigate this issue. We will share updates as they become available.
investigating
We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.
Delays delivering log drains
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.
identified
We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.
identified
We've identified the issue and are working on a fix. We will provide updates as they become available.
investigating
We continue to investigate this issue and will provide updates as they become available.
investigating
We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.
July 2026
Vercel Community temporarily unavailable
Source not attested
Last archived state: resolved
View archived record details
investigating
The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.
Timeouts loading charts and observability data in Dashboard
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor.
investigating
We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.
Dashboard authentication errors
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue causing the dashboard to be inaccessible for some users.
Increased invocation failures for Hobby Team functions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.
identified
We have identified the source of errors and are implementing a fix.
investigating
There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.
GitHub-linked deployments and authentication affected
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered.
identified
We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.
investigating
We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.
SAML Single Sign-On (SSO) errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor.
investigating
We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.
