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.
May 2026
React Router 7 function invocation errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor.
identified
We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover.
identified
The issue has been identified and a fix is being implemented.
investigating
We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.
Support cases cannot be submitted
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix. New support cases can be created. We continue to monitor.
investigating
We are investigating an issue where support cannot be submitted through the dashboard.
Workflow usage amounts are incorrectly calculated
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor.
identified
We are continuing to work on the fix. Usage tracking for Workflow Storage remains paused. The incorrect calculations will not be charged.
identified
The team has identified the source of the incorrect usage data calculations and has paused usage tracking while a fix is being prepared.
investigating
Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.
Vercel Queues, and Vercel Workflow runs were delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.
Delays Processing Builds
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix and are observing recovery across all builds. We'll provide additional updates as-needed.
identified
We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they become available.
Elevated errors across multiple services in IAD1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours.
identified
New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated.
identified
We are continuing to work on a fix for this issue.
identified
New messages to Vercel Workflows and Vercel Queues are being queued, but message processing is paused. Queued messages will be processed when service is restored.
identified
Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1.
identified
Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.
Elevated Errors Creating New Deployments
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes available.
Increased error rate in Workflows
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue and are implementing a fix.
Failures to load data across multiple services on the Vercel dashboard, API, and CLI
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
All systems are operational. We are continuing to monitor the backfill process, which is expected to take a couple of hours. New data is being processed as expected.
monitoring
We are continuing to monitor for any further issues.
monitoring
Impacted services have recovered. We are continuing to monitoring, while backfilling remaining missing data.
identified
Reading data from impacted services has recovered. We are working to backfill any missing data in Observability.
identified
We are seeing services start to recover as we incrementally apply the fix.
identified
We are continuing to work on a fix for this issue.
identified
We've identified an issue where various services in the Vercel dashboard, API, and CLI are failing to load data. These services include Observability, Speed Insights, Alerts, Usage, Web Analytics, Firewall, and CDN observability. Broadly, areas backed by analytical data are affected.
We have identified the issue and are working on a fix.
Production applications running on Vercel are not impacted.
April 2026
Elevated Build Errors
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.
