Vercel Outage History
Past incidents and downtime events
Complete history of Vercel outages, incidents, and service disruptions. Showing 50 most recent incidents.
April 2026(3 incidents)
Elevated INTERNAL_UNEXPECTED_ERROR error rates for some deployments
4 updates
This incident has been resolved.
The fix has been rolled out and we are monitoring the results. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.
We have identified the issue and are rolling out a fix. Deployments created between 16:10 to 19:12 UTC may be affected. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.
We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions
4 updates
This incident has been resolved.
The root cause has been identified, a fix has been rolled out, and we are actively monitoring. Newly deployed Vercel Functions on Node.js 20 in cle1 and dub1 no longer terminate with SIGSEGV. We recommend redeploying affected Vercel Functions if you are still seeing issues.
We are continuing to investigate increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV in Vercel's cle1 and dub1 regions. Other regions are unaffected. We recommend redeploying affected Vercel Functions or upgrading them to either Node js 22 or 24.
We are currently investigating increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV. We recommend redeploying affected Vercel Functions or upgrading them to either Node.js 22 or 24.
Elevated errors creating deployments with integrations and increased delays in delivering webhooks
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.
We have identified an issue causing elevated latency and errors with delivering webhooks and creating deployments that use integrations. We are working on a fix for this issue and will provide further updates as soon as they become available.
March 2026(14 incidents)
Elevated Errors Creating Deployments
3 updates
This incident has been resolved.
A fix has been applied for an issue where deployments were erroring with "invalid request" and we are monitoring the results. We recommend redeploying any failed deployments.
We are investigating reports of elevated errors when creating deployments. Existing deployments and live traffic are unaffected. We will provide updates as they become available.
Degraded Support Case Submission
4 updates
This incident has been resolved.
Support case submission has been confirmed to be functioning normally. We will share updates as they become available.
A fix has been implemented and we are monitoring the results. We will share updates as they become available.
We are currently investigating reports of elevated errors when submitting support cases. Some customers may experience timeouts when creating support tickets. We will share updates as they become available.
Elevated Dashboard Errors
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating reports of elevated error rates on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated Errors Loading Deployments on Dashboard
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating reports of elevated error rates loading the Deployment Overview on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated errors creating Vercel Functions in sin1 (Singapore)
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are observing elevated errors creating Vercel Functions in the `sin1` region. To mitigate errors creating deployments, we have temporarily disabled provisioning new Vercel Functions in this region. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Dubai region (dxb1) is unavailable and traffic is being re-routed
3 updates
Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available.
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.
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 automatically routed to the nearest region based on the configured settings.
Elevated Build Errors
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating elevated error reports of deployment creation during the build phase. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated GitHub Deployment Failures
1 update
Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to GitHub API degradations, which they have since resolved. https://www.githubstatus.com/incidents/lw6j95nyw3py https://www.githubstatus.com/incidents/02z04m335tvv
Elevated Errors on Middleware Invocations
4 updates
This incident has been resolved.
A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.
We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.
Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.
Elevated Latency on Queue Messages, Increased Message Retry Latency in iad1
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are investigating reports of elevated queue message latency and message retry latency in iad1, as well as elevated sleep times and increased step retries in Workflow. We will provide additional updates as they become available.
Delays Loading Observability, Usage, Analytics, and Speed Insights Data
3 updates
This incident has been resolved.
A fix has been implemented and we are seeing recovery for data loading and ingestion across services. We are continuing to monitor and will provide additional updates as they become available.
Dashboard pages that use Observability data, including Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity, are experiencing delays while loading data. These pages are also experiencing delays ingesting new data. We are investigating this issue and will provide additional updates as they become available.
Elevated deployment and function invocations failures
8 updates
This incident has been resolved.
We have rolled out a second mitigation for elevated Build errors and are seeing recovery. All builds are now excluding the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
We have rolled out a first mitigation for elevated Build errors. Builds that use Middleware are now excluding the Dubai region (dxb1) from their deployment targets as a temporary measure, and should complete successfully again. We are now working on a mitigation for Builds that are using Edge Functions.
We are currently deploying a mitigation for elevated Build errors. Builds that use Middleware or Edge Functions will exclude the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
We are still seeing elevated errors in Builds in all regions, because Middleware and Edge Functions may be deployed globally. Builds that don't use Middleware and Edge Functions are not impacted. We are continuing to work on a fix for this issue.
The dxb1 Edge traffic is currently being rerouted to the nearest Edge region (bom1) to mitigate the impact. We will provide additional updates as they become available.
We have rolled out mitigations and are seeing recovery. If you are still seeing build failures and are using Dubai (dxb1) as your primary Vercel Functions region, you can switch to another region as a workaround.
Starting from 5:00 am UTC, we have started seeing failures to deploy and invoke functions in Dubai region (dxb1). Deployments with Middleware Functions are also impacted in all regions, because Middleware Functions are deployed globally for production deployments. Our team is actively investigating the issue.
Degraded Logs and Traces in Dubai region (dxb1)
4 updates
This incident was resolved.
The dxb1 Edge traffic is currently being rerouted to the nearest Edge region (bom1) to mitigate the impact. We will provide additional updates as they become available.
We are continuing to work on a fix for this issue.
We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become available.
Deployments are failing for customers using Static IPs in Dubai region (dxb1)
2 updates
A fix has been implemented and new deployments are no longer failing.
Deployments for customers that use Static IPs are failing when deploying functions to the Dubai region. Customers can remove the Dubai region from the Static IPs configuration to avoid deployment failures. Our team is actively investigating the issue. Deployments to other regions are not affected.
February 2026(9 incidents)
Delays Loading Observability, Analytics and Speed Insights Data
2 updates
This incident has been resolved.
We experienced delays in loading Observability, Analytics and Speed Insights data on the dashboard. We will provide additional updates as they become available.
Delayed Firewall Observability Data
4 updates
The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.
The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.
The issue with delayed firewall observability data has been identified. New data has recovered and old data may be delayed.
We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Elevated Error Rate on AI Gateway in cle1 and fra1
1 update
On February 11, 2026, between 15:00 and 19:26 UTC, AI Gateway experienced elevated error rates due to an issue affecting Vercel Functions infrastructure in the cle1 and fra1 Vercel Regions. Requests routed to these regions, including requests originating from other regions, may have experienced failed requests or timeouts during this time. We have resolved the issue, and the service is now operating normally. We apologize for the disruption.
Problems Loading Dashboard & Elevated Builds Error Rate
4 updates
This incident has been resolved.
We have applied a fix and are seeing recovery across builds and dashboard. We are continuing to monitor.
We have identified the issue and begun applying a fix. We are beginning to see partial recovery across builds and parts of the dashboard. We will provide additional updates as they become available.
We are investigating elevated dashboard load times and error rates on builds. We will provide updates as they become available.
Delays Loading Firewall, Billing, and Observability Data
5 updates
This incident has been resolved.
A fix has been implemented and we are beginning to see gradual recovery. We are actively monitoring results and will share more updates as they become available.
We are continuing to implement a fix for delays in data appearing in the dashboard for firewall, billing, and observability. We will share additional updates as they become available.
The issue has been identified and a fix is being implemented.
We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Elevated Error Rates on Sandboxes
5 updates
This issue has been resolved and sandboxes are creating normally.
A fix has been implemented and we are monitoring the results.
We are releasing a fix and are continuing to work on stabilizing sandbox creation.
We are continuing to work on a fix for this issue.
We have identified an issue while creating new sandboxes. We are working on a fix for the issue.
Elevated latency creating new deployments
3 updates
The issue has been resolved and all deployments are building normally.
A fix has been applied resolving the queue for new deployments. We are continuing to monitor the results.
We are investigating elevated latency creating new deployments. Some deployments may be delayed.
Elevated Errors on API & Dashboard, Delayed Builds
6 updates
This incident has been resolved.
A fix has been implemented, and we are monitoring results.
We have begun applying fixes and are seeing partial recovery across API, dashboard, and builds. We are continuing to apply fixes. We will share additional updates as they become available.
The issue has been identified, and we are working on a fix.
We are continuing to investigate this issue.
We are currently investigating reports of elevated error rates and slowness on the Vercel Dashboard and APIs. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated error rates in sin1 (Singapore) Edge Region
1 update
There were elevated error rates in the sin1 (Singapore) edge region between 08:57 and 09:04 UTC. The issue has been resolved, and all systems are operating normally.
January 2026(5 incidents)
Elevated git clone duration at build time
7 updates
This incident has been resolved.
The new build routing has addressed the issue. We are monitoring the results.
We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We’ve confirmed the issue is intermittent, and redeploying a failed build may succeed. Alternatively, as a temporary workaround, builds can be run locally and deployed as prebuilt output using Vercel CLI: `vercel build && vercel deploy --prebuilt`
We are currently observing elevated `git clone` durations on a subset of builds. Some builds are taking significantly longer than expected to clone repositories, resulting in slower overall build start times. We are actively analyzing clone performance metrics and infrastructure behavior to identify the root cause.
Elevated Connection Latency in dub1 (Dublin, Ireland) Edge Region
5 updates
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
Delayed Dashboard Data Across Multiple Services
5 updates
This incident has been resolved.
A fix is currently being rolled out. Most customers should now be seeing recovery, and we expect this incident to be fully resolved shortly.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating reports of delayed metrics for Observability, Speed Insights, Web Analytics, Usage, and Audit Logs. We will share updates as they become available.
Some domain purchases are failing
4 updates
After monitoring, we do not see the issue persisting. This incident is resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating an issue where some domain purchases are failing.
Elevated build failure rates
4 updates
After monitoring our fix, we found no new occurrences of build errors. This issue has been resolved.
A fix has been implemented and we are monitoring the results.
We're continuing to investigate this issue and will provide further updates as soon as they become available.
We've identified an issue causing builds to fail for some projects. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
December 2025(7 incidents)
Errors creating Support Center cases
3 updates
This incident has been resolved.
We've identified the issue, and we are working on a fix. Vercel customers should be able to create cases normally while we monitor case operation metrics closely.
We are investigating an issue with creating new Support Center cases. For affected Enterprise customers, please escalate out to Vercel contacts via Slack or email for support. For Pro and Hobby customers, please use the Vercel Community: https://community.vercel.com/
Web Analytics and Speed insights data not recorded on some projects
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
On some projects, traffic is miscategorised and not recorded on Speed Insights and Web Analytics
Elevated error rates across new deployments and Vercel API
3 updates
Vercel API errors have been resolved and dashboard access is restored across all regions. Queued deployments are recovering automatically, but failed deployments may need to be redeployed manually.
We are continuing to investigate this issue.
We are currently investigating reports of elevated errors for new deployments, Vercel API, and Vercel dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated errors creating deployments with Neon and Supabase integrations
4 updates
This incident has been resolved.
Deployments using the Supabase integration are now working as expected. We are continuing to work on `Resource provisioning timed out` errors related to the Neon integration.
We've identified a potential root cause in our webhook service affecting the build process. We will continue to provide further updates as we learn more.
We are currently investigating intermittent `Resource provisioning timed out` errors that occur when creating new deployments with the Neon or Supabase integration. Existing deployments are not affected.
Elevated errors loading Vercel Logs and Speed Insights
1 update
We received reports of elevated errors loading Vercel Logs and Speed Insights at 21:15 UTC. A fix was released at 21:25 UTC, and full functionality was restored by 21:38 UTC.
Speed Insights elevated errors
4 updates
This incident has been resolved.
The fix has been released, and we're observing recovery in loading Speed Insights data.
The issue has been identified, and a fix is in progress.
We are currently investigating reports of elevated errors loading Speed Insights data.
Elevated Error Rates for Domain Registrations
4 updates
The issue causing elevated error rates for Domain Registrations has been resolved. Domains are now successfully provisioned and available for immediate use. Some payment attempts may not have completed; we will automatically retry those payments later. No action is needed from customers.
We have deployed a fix for the issue affecting Domain Registrations and are currently monitoring the service to ensure stability.
We have identified the cause of the elevated error rates affecting Domain Registrations, and we are currently implementing a fix.
We are currently investigating elevated error rates affecting Domain Registrations. All existing domains, DNS functionality, deployments, and live traffic remain fully operational. We will provide additional updates as more information becomes available.
November 2025(9 incidents)
Elevated errors creating deployments
4 updates
This incident has been resolved.
The fix has been released, and we are monitoring the results.
We have identified the issue and are implementing a fix.
We are currently investigating reports of elevated errors during deployment creation. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated error rate for domain search and registration
6 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Domain search and registration are still impacted. We are investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are currently investigating this issue.
Builds and Deployments were Temporarily in a Queued State
1 update
Builds and deployments were stuck in a queued state between 10:05 to 10:30 UTC. Our team identified the root cause and deployed a fix, and everything is now operating normally.
Builds and Deployments are Currently in a Queued State
3 updates
This incident has been resolved.
The issue has been identified and a fix is being implemented.
All builds are stuck in a queued state. Our team is currently investigating this issue. Live deployments are not affected.
Elevated errors serving traffic in dub1 Edge Region
2 updates
This incident has been resolved.
We are currently investigating this issue.
Runtime logs not showing in Dashboard
1 update
A change was merged to the Vercel dashboard that introduced a bug in the query for runtime logs in some situations. Upon being alerted, the dashboard was rolled back, which restored the ability to see runtime logs. The change was then reverted. Data was still being collected and no logs are missing.
Builds and Deployments are Currently in a Queued State
3 updates
This incident has been resolved.
We have identified the issue and are working to process the backlog of queued builds.
All builds are stuck in a queued state. Our team is currently investigating this issue. Live deployments are not affected.
AI Gateway is unavailable
4 updates
This incident has been resolved.
We have implemented a fix and are seeing no errors as of 20:26 UTC.
We are continuing to investigate this issue.
AI Gateway model requests and metadata API calls are unavailable.
Elevated errors for Edge Config
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Some customers are experiencing an elevated rate of HTTP errors for Edge Config.
October 2025(3 incidents)
Intermittent errors affecting APIs and new builds
3 updates
The issue has been fully mitigated, and this incident has been resolved. No action is needed for customers with queued builds.
We have identified the root cause of the issue and have deployed a fix.
We are investigating an issue causing intermittent errors from our public APIs and impacting new builds. Existing deployments are not impacted.
Intermittent failures for builds using Secure Compute or Static IPs
5 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We're seeing recovery for this issue. Users can redeploy the affected deployments.
New deployments that use Secure Compute or Static IPs are currently experiencing intermittent failures. We've identified the issue and are working to resolve this. Users will need to redeploy affected deployments after the issue is resolved. Existing deployments are not affected.
On-Demand Usage Invoices Delayed
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
Issuance of on-demand usage invoices is currently delayed. We’re working to resolve this and expect the delayed invoices to be issued within the next 24 hours.
📡 Tired of checking Vercel status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Vercel goes down.