Vercel Outage History
Vercel is up right nowPingoru has recorded 125 incidents for Vercel: 125 in the last 12 months and 23 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 18 | 41 of 720 (6%) |
| May 2026 | 19 | 52 of 744 (7%) |
| June 2026 | 9 | 24 of 720 (3%) |
| July 2026 | 14 | 41 of 744 (5%) |
| August 2026 | 8 | 20 of 744 (3%) |
| September 2026 | 10 | 10 of 720 (1%) |
| October 2026 | 5 | 10 of 585 (2%) |
Incidents, newest first
Minor April 2, 2026 Elevated INTERNAL_UNEXPECTED_ERROR error rates for some deployments 4h 29m Builds
Started Apr 02, 2026, 06:39 PM UTC· resolved Apr 02, 2026, 11:09 PM UTC
- investigating Apr 02, 2026, 06:39 PM UTC
We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
- identified Apr 02, 2026, 07:26 PM UTC
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.
- monitoring Apr 02, 2026, 08:02 PM UTC
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.
- resolved Apr 02, 2026, 11:09 PM UTC
This incident has been resolved.
Minor April 2, 2026 Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions 4h 43m Functions
Started Apr 02, 2026, 02:10 PM UTC· resolved Apr 02, 2026, 06:53 PM UTC
- investigating Apr 02, 2026, 02:10 PM UTC
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.
- investigating Apr 02, 2026, 04:13 PM UTC
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.
- monitoring Apr 02, 2026, 06:09 PM UTC
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.
- resolved Apr 02, 2026, 06:53 PM UTC
This incident has been resolved.
Minor April 1, 2026 Elevated errors creating deployments with integrations and increased delays in delivering webhooks 1h 29m Builds
Started Apr 01, 2026, 08:48 PM UTC· resolved Apr 01, 2026, 10:17 PM UTC
- identified Apr 01, 2026, 08:48 PM UTC
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.
- monitoring Apr 01, 2026, 09:57 PM UTC
A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.
- resolved Apr 01, 2026, 10:17 PM UTC
This incident has been resolved.
Major March 31, 2026 Elevated Errors Creating Deployments 11m Builds
Started Mar 31, 2026, 09:11 PM UTC· resolved Mar 31, 2026, 09:23 PM UTC
- investigating Mar 31, 2026, 09:11 PM UTC
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.
- monitoring Mar 31, 2026, 09:17 PM UTC
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.
- resolved Mar 31, 2026, 09:23 PM UTC
This incident has been resolved.
Major March 31, 2026 Degraded Support Case Submission 12m Support Center
Started Mar 31, 2026, 01:16 PM UTC· resolved Mar 31, 2026, 01:29 PM UTC
- investigating Mar 31, 2026, 01:10 PM UTC
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.
- monitoring Mar 31, 2026, 01:16 PM UTC
A fix has been implemented and we are monitoring the results. We will share updates as they become available.
- monitoring Mar 31, 2026, 01:16 PM UTC
Support case submission has been confirmed to be functioning normally. We will share updates as they become available.
- resolved Mar 31, 2026, 01:29 PM UTC
This incident has been resolved.
Minor March 25, 2026 Elevated Dashboard Errors 59m Dashboard, Builds, API
Started Mar 25, 2026, 04:32 PM UTC· resolved Mar 25, 2026, 05:31 PM UTC
- investigating Mar 25, 2026, 04:32 PM UTC
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.
- monitoring Mar 25, 2026, 04:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 25, 2026, 05:31 PM UTC
This incident has been resolved.
Minor March 24, 2026 Elevated Errors Loading Deployments on Dashboard 1h 11m Dashboard
Started Mar 24, 2026, 03:19 PM UTC· resolved Mar 24, 2026, 04:31 PM UTC
- investigating Mar 24, 2026, 03:19 PM UTC
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.
- monitoring Mar 24, 2026, 04:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 24, 2026, 04:31 PM UTC
This incident has been resolved.
Minor March 24, 2026 Elevated errors creating Vercel Functions in sin1 (Singapore) 1h 18m Builds
Started Mar 24, 2026, 03:43 AM UTC· resolved Mar 24, 2026, 05:01 AM UTC
- identified Mar 24, 2026, 03:43 AM UTC
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.
- monitoring Mar 24, 2026, 04:40 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 24, 2026, 05:01 AM UTC
This incident has been resolved.
Notice March 12, 2026 Elevated GitHub Deployment Failures –
Started Mar 12, 2026, 01:15 AM UTC· resolved Mar 12, 2026, 01:15 AM UTC
- resolved Mar 12, 2026, 06:17 AM UTC
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
Minor March 6, 2026 Elevated Latency on Queue Messages, Increased Message Retry Latency in iad1 28m Queues, Workflow
Started Mar 06, 2026, 08:53 PM UTC· resolved Mar 06, 2026, 09:22 PM UTC
- investigating Mar 06, 2026, 08:53 PM UTC
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.
- identified Mar 06, 2026, 09:00 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 06, 2026, 09:10 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 06, 2026, 09:22 PM UTC
This incident has been resolved.
Minor March 6, 2026 Elevated Errors on Middleware Invocations 6h 12m Routing Middleware
Started Mar 06, 2026, 03:25 PM UTC· resolved Mar 06, 2026, 09:38 PM UTC
- identified Mar 06, 2026, 03:25 PM UTC
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.
- identified Mar 06, 2026, 07:18 PM UTC
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.
- monitoring Mar 06, 2026, 09:20 PM UTC
A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.
- resolved Mar 06, 2026, 09:38 PM UTC
This incident has been resolved.
Minor March 3, 2026 Delays Loading Observability, Usage, Analytics, and Speed Insights Data 4h Dashboard, Speed Insights, Web Analytics
Started Mar 03, 2026, 05:10 PM UTC· resolved Mar 03, 2026, 09:10 PM UTC
- investigating Mar 03, 2026, 05:10 PM UTC
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.
- monitoring Mar 03, 2026, 07:14 PM UTC
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.
- resolved Mar 03, 2026, 09:10 PM UTC
This incident has been resolved.
Minor March 2, 2026 Dubai region (dxb1) is unavailable and traffic is being re-routed 14d 3h DXB1 - Dubai, UAE
Started Mar 02, 2026, 03:29 PM UTC· resolved Mar 16, 2026, 06:44 PM UTC
- identified Mar 02, 2026, 03:29 PM UTC
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.
- monitoring Mar 02, 2026, 06:23 PM UTC
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.
- resolved Mar 16, 2026, 06:44 PM UTC
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.
Minor March 2, 2026 Degraded Logs and Traces in Dubai region (dxb1) 5h 14m Logs, Drains
Started Mar 02, 2026, 06:54 AM UTC· resolved Mar 02, 2026, 12:08 PM UTC
- investigating Mar 02, 2026, 06:54 AM UTC
We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become available.
- identified Mar 02, 2026, 08:01 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 02, 2026, 08:49 AM UTC
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.
- resolved Mar 02, 2026, 12:08 PM UTC
This incident was resolved.
Minor March 2, 2026 Elevated deployment and function invocations failures 9h 14m Builds, Edge Functions, Routing Middleware, Functions
Started Mar 02, 2026, 06:06 AM UTC· resolved Mar 02, 2026, 03:20 PM UTC
- identified Mar 02, 2026, 06:06 AM UTC
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.
- identified Mar 02, 2026, 06:24 AM UTC
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.
- identified Mar 02, 2026, 07:56 AM UTC
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.
- identified Mar 02, 2026, 10:50 AM UTC
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.
- identified Mar 02, 2026, 11:59 AM UTC
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.
- identified Mar 02, 2026, 01:00 PM UTC
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.
- monitoring Mar 02, 2026, 02:59 PM UTC
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.
- resolved Mar 02, 2026, 03:20 PM UTC
This incident has been resolved.
Major March 1, 2026 Deployments are failing for customers using Static IPs in Dubai region (dxb1) 3h 4m Builds
Started Mar 01, 2026, 09:17 PM UTC· resolved Mar 02, 2026, 12:22 AM UTC
- identified Mar 01, 2026, 09:17 PM UTC
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.
- resolved Mar 02, 2026, 12:22 AM UTC
A fix has been implemented and new deployments are no longer failing.
Notice February 28, 2026 Delays Loading Observability, Analytics and Speed Insights Data 41m Dashboard, Speed Insights, Web Analytics
Started Feb 28, 2026, 05:46 AM UTC· resolved Feb 28, 2026, 06:28 AM UTC
- monitoring Feb 28, 2026, 05:46 AM UTC
We experienced delays in loading Observability, Analytics and Speed Insights data on the dashboard. We will provide additional updates as they become available.
- resolved Feb 28, 2026, 06:28 AM UTC
This incident has been resolved.
Minor February 12, 2026 Delayed Firewall Observability Data 4h 14m Dashboard, Firewall
Started Feb 12, 2026, 10:41 PM UTC· resolved Feb 13, 2026, 02:56 AM UTC
- investigating Feb 12, 2026, 10:41 PM UTC
We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
- monitoring Feb 12, 2026, 10:59 PM UTC
The issue with delayed firewall observability data has been identified. New data has recovered and old data may be delayed.
- monitoring Feb 13, 2026, 01:52 AM 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.
- resolved Feb 13, 2026, 02:56 AM 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.
Notice February 11, 2026 Elevated Error Rate on AI Gateway in cle1 and fra1 –
Started Feb 11, 2026, 03:00 PM UTC· resolved Feb 11, 2026, 03:00 PM UTC
- resolved Feb 11, 2026, 09:28 PM UTC
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.
Major February 7, 2026 Problems Loading Dashboard & Elevated Builds Error Rate 2h 39m Dashboard, Builds
Started Feb 07, 2026, 08:38 AM UTC· resolved Feb 07, 2026, 11:18 AM UTC
- investigating Feb 07, 2026, 08:38 AM UTC
We are investigating elevated dashboard load times and error rates on builds. We will provide updates as they become available.
- identified Feb 07, 2026, 09:35 AM UTC
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.
- monitoring Feb 07, 2026, 10:23 AM UTC
We have applied a fix and are seeing recovery across builds and dashboard. We are continuing to monitor.
- resolved Feb 07, 2026, 11:18 AM UTC
This incident has been resolved.
Minor February 5, 2026 Delays Loading Firewall, Billing, and Observability Data 4h 39m Dashboard
Started Feb 05, 2026, 04:11 PM UTC· resolved Feb 05, 2026, 08:51 PM UTC
- investigating Feb 05, 2026, 04:11 PM UTC
We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
- identified Feb 05, 2026, 04:53 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 05, 2026, 06:28 PM UTC
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.
- monitoring Feb 05, 2026, 07:35 PM UTC
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.
- resolved Feb 05, 2026, 08:51 PM UTC
This incident has been resolved.
Minor February 3, 2026 Elevated latency creating new deployments 48m Builds
Started Feb 03, 2026, 08:47 PM UTC· resolved Feb 03, 2026, 09:36 PM UTC
- investigating Feb 03, 2026, 08:48 PM UTC
We are investigating elevated latency creating new deployments. Some deployments may be delayed.
- monitoring Feb 03, 2026, 09:12 PM UTC
A fix has been applied resolving the queue for new deployments. We are continuing to monitor the results.
- resolved Feb 03, 2026, 09:36 PM UTC
The issue has been resolved and all deployments are building normally.
Minor February 3, 2026 Elevated Error Rates on Sandboxes 3h 15m Sandbox
Started Feb 03, 2026, 06:38 PM UTC· resolved Feb 03, 2026, 09:54 PM UTC
- identified Feb 03, 2026, 06:38 PM UTC
We have identified an issue while creating new sandboxes. We are working on a fix for the issue.
- identified Feb 03, 2026, 06:49 PM UTC
We are continuing to work on a fix for this issue.
- identified Feb 03, 2026, 07:51 PM UTC
We are releasing a fix and are continuing to work on stabilizing sandbox creation.
- monitoring Feb 03, 2026, 08:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 03, 2026, 09:54 PM UTC
This issue has been resolved and sandboxes are creating normally.
Major February 3, 2026 Elevated Errors on API & Dashboard, Delayed Builds 2h 7m Dashboard, Builds, API
Started Feb 03, 2026, 03:22 PM UTC· resolved Feb 03, 2026, 05:30 PM UTC
- investigating Feb 03, 2026, 03:22 PM UTC
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.
- investigating Feb 03, 2026, 03:43 PM UTC
We are continuing to investigate this issue.
- identified Feb 03, 2026, 03:43 PM UTC
The issue has been identified, and we are working on a fix.
- identified Feb 03, 2026, 04:22 PM UTC
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.
- monitoring Feb 03, 2026, 04:50 PM UTC
A fix has been implemented, and we are monitoring results.
- resolved Feb 03, 2026, 05:30 PM UTC
This incident has been resolved.
Notice February 1, 2026 Elevated error rates in sin1 (Singapore) Edge Region –
Started Feb 01, 2026, 08:57 AM UTC· resolved Feb 01, 2026, 08:57 AM UTC
- resolved Feb 01, 2026, 10:15 AM UTC
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.