Vercel Outage History
Uptime record, past incidents, and downtime history for Vercel.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 70% | 10 | 3 |
| March 2026 | 35.5% | 31 | 20 |
| February 2026 | 82.1% | 28 | 5 |
| January 2026 | 100% | 1 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 70 Days)
Jan 31
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
Elevated queue times for deployments on the Hobby plan
Started: Apr 7, 6:06 PM
identified
A fix has been rolled out, and we are monitoring the results. Queued deployments are being processed and new deployments are building normally now.
Apr 7, 6:27 PM
identified
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.
Apr 7, 6:06 PM
Builds logs stuck in loading state
Started: Apr 7, 7:19 AM
investigating
We are investigating reports of build logs stuck in loading state.
Apr 7, 7:19 AM
Elevated INTERNAL_UNEXPECTED_ERROR error rates for some deployments
Started: Apr 2, 6:39 PM
monitoring
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.
Apr 2, 8:02 PM
identified
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.
Apr 2, 7:26 PM
investigating
We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
Apr 2, 6:39 PM
Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions
Started: Apr 2, 2:10 PM
monitoring
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.
Apr 2, 6:09 PM
investigating
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.
Apr 2, 4:13 PM
investigating
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.
Apr 2, 2:10 PM
Elevated errors creating deployments with integrations and increased delays in delivering webhooks
Started: Apr 1, 8:48 PM
monitoring
A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.
Apr 1, 9:57 PM
identified
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.
Apr 1, 8:48 PM
March 2026
Elevated Errors Creating Deployments
Started: Mar 31, 9:11 PM
monitoring
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.
Mar 31, 9:17 PM
investigating
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.
Mar 31, 9:11 PM
Degraded Support Case Submission
Started: Mar 31, 1:16 PM
monitoring
Support case submission has been confirmed to be functioning normally. We will share updates as they become available.
Mar 31, 1:16 PM
monitoring
A fix has been implemented and we are monitoring the results. We will share updates as they become available.
Mar 31, 1:16 PM
investigating
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.
Mar 31, 1:10 PM
Elevated Dashboard Errors
Started: Mar 25, 4:32 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 25, 4:41 PM
investigating
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.
Mar 25, 4:32 PM
Elevated Errors Loading Deployments on Dashboard
Started: Mar 24, 3:19 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 24, 4:14 PM
investigating
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.
Mar 24, 3:19 PM
Elevated errors creating Vercel Functions in sin1 (Singapore)
Started: Mar 24, 3:43 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 24, 4:40 AM
identified
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.
Mar 24, 3:43 AM
Elevated Build Errors
Started: Mar 13, 10:32 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 13, 10:53 PM
investigating
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.
Mar 13, 10:32 PM
Dubai region (dxb1) is unavailable and traffic is being re-routed
Started: Mar 2, 3:29 PM
monitoring
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.
Mar 2, 6:23 PM
identified
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 automatic...
Mar 2, 3:29 PM