Is Vercel Down?

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 - The issue has been identified and a fix is being implemented. Jun 26 , 14:08 UTC Update - We are continuing to investigate this issue and will provide an update as soon as we have more information. Jun 26 , 13:23 UTC Update - We are continuing to investigate this issue. Jun 26 , 13:08 UTC Investigating - We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.

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 Update - We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs. Jun 25 , 09:25 UTC Update - The issue has been identified. We are continuing to work on a fix for this issue. Jun 25 , 08:27 UTC Identified - The issue has been identified and a fix is being implemented. Jun 25 , 07:45 UTC Investigating - We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.

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. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.

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 Identified - The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. Jun 16 , 14:45 UTC Update - We are continuing to investigate partial disruption to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are also investigating delayed usage alerts. Jun 16 , 13:39 UTC Investigating - We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.

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 Region. We will provide another status update after this has finished. Jun 14 , 21:26 UTC Update - The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. Jun 14 , 21:07 UTC Identified - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. Jun 14 , 21:03 UTC Investigating - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.

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 are currently investigating this issue.

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 on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region. If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue. Jun 8 , 18:57 UTC Identified - The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.

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 are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

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 identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.