There were 40 Vercel outages since February 3, 2026 totaling 46h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content were unaffected this time. We have reverted the change that caused the issue to mitigate this.
We are currently investigating this issue.
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 are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating an issue causing elevated error rates across domains operations, including renewals, nameserver changes, search, and checkout. We will provide additional updates as they become available.
A fix has been applied and we are seeing signs of recovery across domains operations. We are continuing to monitor and will provide additional updates as needed.
This incident has been resolved.
We're investigating reports of unexpected errors when trying to create and deploy new projects from templates. We will 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.
This incident has been resolved.
We have identified an issue resulting in delayed and/or missing usage data for observability events between 9:00 - 10:30 UTC and 16:50 - 19:30 UTC. The issue has been identified and resolved, and we are working to backfill missing the data for the affected time buckets. No additional actions are required for customers at this time.
We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period. All underlying compute services - including Vercel Functions, Workflows, and Cron Jobs - continued to operate normally. Logs were not affected and remain fully available.
We're investigating reports of customers being unable to checkout with domains purchases. We'll provide additional updates as they become available.
We're continuing to investigate reports of customers being unable to checkout with domains purchases. We're also investigating reports of being unable to purchase AI gateway credits. 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.
This incident has been resolved.
We're investigating an issue causing delays in loading logs. We will provide additional updates as they become available.
The issue has been identified and a fix is being implemented.
We are continuing to implement a fix for the issue causing delays in load logs. We will provide additional updates as they become available.
We are continuing to implement a fix for the issue causing delays in loading logs. We will provide additional updates as they become available.
A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.
We've identified an additional issue causing delays in loading logs. We'll provide additional updates as they become available.
A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.
This incident has been resolved.
We are currently investigating this issue.
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 have identified an issue causing elevated error rates on the Vercel Dashboard and API endpoints. Some users may experience an issue creating new deployments, but existing deployments are not impacted. We will share more updates as they become available.
A fix has been implemented and we are observing recovery in error rates across the Vercel Dashboard and API endpoints. We will continue to monitor and share any additional updates as they become available.
This incident has been resolved.
We are currently investigating runtime logs not loading properly in the dashboard. We will share more updates as soon as we have more information.
A fix has been implemented and we are monitoring the result. Please refresh your browser page if you are not seeing runtime logs.
This incident has been resolved.
We are currently investigating Observability Alerts not detecting new alerts.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We have resolved the issue for error anomalies, and are continuing to work on a fix for usage anomalies.
We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.
We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.
We have implemented a fix targeted at usage anomalies and are now observing recovery across all anomaly alerts. We will share any additional updates as-needed.
This incident has been resolved.
We are currently experiencing delays in loading Observability, Analytics and Speed Insights data on the dashboard. This may also affect User Activity Events and Firewall UI. We will 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 seeing recovery. No action is required - data may continue to be partially delayed as it is backfilled.
This incident has been resolved.
We have identified an issue causing elevated queue times for deployments on the Hobby plan. We are investigating a fix and will share more updates as soon as we have more information.
A fix has been rolled out, and we are monitoring the results. Queued deployments are being processed and new deployments are building normally now.
This incident has been resolved.
We are investigating reports of build logs stuck in loading state.
We identified the cause of build logs stuck in the loading state affecting iad1 and are working around the issue for new builds. Please redeploy to your build to view build logs.
The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy.
We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
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.
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.
This incident has been resolved.
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.
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.
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.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.
This incident has been resolved.
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.
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.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results. We will share updates as they become available.
Support case submission has been confirmed to be functioning normally. We will share updates as they become available.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
Pingoru polls Vercel's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required