Vercel Status - Incident History

3 days ago

Jul 10, 23:28 UTC Resolved - This incident has been resolved. Jul 10, 21:22 UTC Monitoring - We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become av

Erroneous budget notifications

4 days ago

Jul 10, 22:36 UTC Resolved - We have unpaused all impacted deployments. We will continue to monitor the situation. Jul 10, 21:32 UTC Update - We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation. We will provide additional

Delays loading Build Logs

5 days ago

Jul 9, 13:16 UTC Resolved - The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.

Delays Processing Builds

6 days ago

Jul 8, 19:13 UTC Resolved - This incident has been resolved. Jul 8, 19:13 UTC Update - The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis. Jul 8,

Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)

12 days ago

Jul 2, 16:46 UTC Resolved - This incident has been resolved. Jul 2, 16:39 UTC Monitoring - A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor. Jul 2, 16:33 UTC Identified - The is

Increase in Workflow runs stuck in pending, failed

13 days ago

Jul 1, 18:30 UTC Resolved - The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs t

Intermittent Login Failures on Vercel Dashboard

18 days ago

Jun 26, 15:14 UTC Resolved - This incident has been resolved. Jun 26, 15:03 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 26, 14:29 UTC Update - Login is recovering for most users. We're monitoring to ensure stability. Jun 26, 14:11 UTC Identified -

Increase in Workflow runs stuck as pending

19 days ago

Jun 25, 13:43 UTC Resolved - This incident has been resolved. Jun 25, 13:30 UTC Monitoring - The fix has been fully rolled out and we are monitoring the results. Jun 25, 12:15 UTC Update - We are currently rolling a fix for the issue. We are monitoring the results. Jun 25, 10:42 UTC Upd

Degraded Domain Search in Vercel Dashboard

20 days ago

Jun 23, 23:34 UTC Resolved - This incident has been resolved. Jun 23, 23:28 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 23, 23:26 UTC Identified - The issue has been identified and a fix is being implemented. Jun 23, 23:24 UTC Investigating - We're

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

25 days ago

Jun 19, 17:54 UTC Resolved - Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions

Partial disruption of Observability, Analytics, Firewall, and Usage in dashboard

Jun 16, 15:39 UTC Resolved - The incident has been resolved. Jun 16, 15:26 UTC Monitoring - The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor. Jun 16, 15:16 UTC

Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)

Jun 15, 01:24 UTC Resolved - This incident has been resolved. Jun 15, 00:25 UTC Monitoring - All traffic has been restored to the FRA1 Vercel Region. Jun 14, 23:15 UTC Update - The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel

Elevated Build Errors for Secure Compute/Static IPs Projects

Jun 9, 14:46 UTC Resolved - This incident has been resolved. Jun 9, 14:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 9, 14:33 UTC Identified - The issue has been identified and a fix is being implemented. Jun 9, 14:09 UTC Investigating - We ar

Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region

Jun 8, 20:00 UTC Resolved - This incident has been resolved. Jun 8, 19:36 UTC Update - We are continuing to monitor for any further issues. Jun 8, 19:36 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 8, 19:04 UTC Update - We're continuing to work

Elevated Errors Creating New Deployments

Jun 1, 20:02 UTC Resolved - This incident has been resolved. Jun 1, 19:55 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 1, 19:50 UTC Identified - The issue has been identified and a fix is being implemented. Jun 1, 19:21 UTC Investigating - We ar

Elevated Function Invocation Errors in Stockholm region (ARN1)

May 28, 16:59 UTC Resolved - This incident has been resolved. May 28, 16:37 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 28, 16:18 UTC Identified - The issue has been identified and a fix is being implemented. May 28, 16:00 UTC Investigating - We've

Elevated Errors on Vercel Dashboard (Project Overview Page)

May 27, 05:02 UTC Resolved - This incident has been resolved. We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC. May 27, 04:50 UTC Investigating - We are currently investigating this issue.

Delays Loading Runtime Logs

May 25, 16:22 UTC Resolved - This incident has been resolved. May 25, 16:05 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 25, 15:25 UTC Identified - The issue has been identified and a fix is being implemented. May 25, 14:58 UTC Investigating - We ar

Elevated Build Failures (GitHub connected projects)

May 23, 18:44 UTC Resolved - This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt May 23, 18:21 UTC Monitoring - GitHub has implemented a fix, and we are monitoring the results. May 23, 15:46 UTC Ide

Build Failures for Some Next.js Deployments

May 22, 17:11 UTC Resolved - Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.

Elevated Build Errors

May 21, 21:31 UTC Resolved - This incident has been resolved. May 21, 21:20 UTC Monitoring - The mitigation was successfully rolled out, and builds are stable. May 21, 19:55 UTC Update - The root cause has been identified and we are rolling out a mitigation. May 21, 15:01 UTC Identified

Missing Build CPU Minutes Usage Data

May 21, 06:08 UTC Resolved - This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window. May 20, 2

Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND

May 18, 23:52 UTC Resolved - This incident has been resolved. Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected. The fi

Support cases cannot be submitted

May 18, 15:41 UTC Resolved - The incident is resolved and support cases can be submitted again. May 18, 15:17 UTC Monitoring - We have implemented a fix. New support cases can be created. We continue to monitor. May 18, 15:00 UTC Investigating - We are investigating an issue where support c

Workflow usage amounts are incorrectly calculated