57 recorded Vercel incidents since May 2026, with official updates, affected components, duration and resolution information.
We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.
The issue causing delays in Logs and Observability data has been resolved.
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.
We have identified the issue and are working on a fix. We will provide additional updates as they become available.
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.
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.
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.
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
This incident has been resolved.
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.
A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.
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.
All services have recovered.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
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.
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.
This incident has been resolved.
We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.
We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.
Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.
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.
Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.
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.
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.
The issue has been identified and a fix is being implemented.
Connect and Passport have fully recovered. This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
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.
The fix has been rolled out and we are seeing signs of recovery.
Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.
Blob has fully recovered. This incident has been resolved.
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.
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.
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.
We are seeing recovery in Builds and are continuing to monitor.
We are continuing to monitor for any further issues.
This incident has been resolved. Builds have recovered.
We are investigating errors logging in with Vercel CLI (vc login).
The team has identified the source of the issue and is testing a fix.
This incident has been resolved.
We're investigating elevated initialization times for some builds. We will provide updates as we learn more.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We have deployed a fix. Newly deployed container functions are working as expected.
This incident has been resolved.
We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.
We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.
The system is operating normally and fully recovered.
From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.
