Jul <var data-var='date'> 2</var>, <var data-var='time'>16:46</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 2</var>, <var data-var='time'>16:39</var> 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 <var data-var='date'> 2</var>, <var data-var='time'>16:33</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'> 2</var>, <var data-var='time'>16:31</var> UTC Investigating - We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.

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

Jul <var data-var='date'> 1</var>, <var data-var='time'>18:30</var> 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 that could not be resumed safely were transitioned to a cancelled state. Jul <var data-var='date'> 1</var>, <var data-var='time'>17:49</var> UTC Update - We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. Jul <var data-var='date'> 1</var>, <var data-var='time'>16:57</var> UTC Identified - We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.

Increase in Workflow runs stuck in pending, failed

Jun <var data-var='date'>26</var>, <var data-var='time'>15:14</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>26</var>, <var data-var='time'>15:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>26</var>, <var data-var='time'>14:29</var> UTC Update - Login is recovering for most users. We're monitoring to ensure stability. Jun <var data-var='date'>26</var>, <var data-var='time'>14:11</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>26</var>, <var data-var='time'>14:08</var> UTC Update - We are continuing to investigate this issue and will provide an update as soon as we have more information. Jun <var data-var='date'>26</var>, <var data-var='time'>13:23</var> UTC Update - We are continuing to investigate this issue. Jun <var data-var='date'>26</var>, <var data-var='time'>13:08</var> UTC Investigating - We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.

Intermittent Login Failures on Vercel Dashboard

Jun <var data-var='date'>25</var>, <var data-var='time'>13:43</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>25</var>, <var data-var='time'>13:30</var> UTC Monitoring - The fix has been fully rolled out and we are monitoring the results. Jun <var data-var='date'>25</var>, <var data-var='time'>12:15</var> UTC Update - We are currently rolling a fix for the issue. We are monitoring the results. Jun <var data-var='date'>25</var>, <var data-var='time'>10:42</var> 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 <var data-var='date'>25</var>, <var data-var='time'>09:25</var> UTC Update - The issue has been identified. We are continuing to work on a fix for this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>08:27</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>25</var>, <var data-var='time'>07:45</var> 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.

Increase in Workflow runs stuck as pending

Jun <var data-var='date'>23</var>, <var data-var='time'>23:34</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>23:28</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>23</var>, <var data-var='time'>23:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>23</var>, <var data-var='time'>23:24</var> UTC Investigating - We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.

Degraded Domain Search in Vercel Dashboard

Jun <var data-var='date'>19</var>, <var data-var='time'>17:54</var> 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.

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

Jun <var data-var='date'>16</var>, <var data-var='time'>15:39</var> UTC Resolved - The incident has been resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>15:26</var> 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 <var data-var='date'>16</var>, <var data-var='time'>15:16</var> 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 <var data-var='date'>16</var>, <var data-var='time'>14:45</var> 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 <var data-var='date'>16</var>, <var data-var='time'>13:39</var> UTC Investigating - We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.

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

Jun <var data-var='date'>15</var>, <var data-var='time'>01:24</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>15</var>, <var data-var='time'>00:25</var> UTC Monitoring - All traffic has been restored to the FRA1 Vercel Region. Jun <var data-var='date'>14</var>, <var data-var='time'>23:15</var> 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 <var data-var='date'>14</var>, <var data-var='time'>21:26</var> 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 <var data-var='date'>14</var>, <var data-var='time'>21:07</var> UTC Identified - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. Jun <var data-var='date'>14</var>, <var data-var='time'>21:03</var> UTC Investigating - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.

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

Jun <var data-var='date'> 9</var>, <var data-var='time'>14:46</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 9</var>, <var data-var='time'>14:39</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 9</var>, <var data-var='time'>14:33</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'> 9</var>, <var data-var='time'>14:09</var> UTC Investigating - We are currently investigating this issue.

Elevated Build Errors for Secure Compute/Static IPs Projects

Jun <var data-var='date'> 8</var>, <var data-var='time'>20:00</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 8</var>, <var data-var='time'>19:36</var> UTC Update - We are continuing to monitor for any further issues. Jun <var data-var='date'> 8</var>, <var data-var='time'>19:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 8</var>, <var data-var='time'>19:04</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>18:57</var> 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.

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

Jun <var data-var='date'> 1</var>, <var data-var='time'>20:02</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 1</var>, <var data-var='time'>19:55</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 1</var>, <var data-var='time'>19:50</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'> 1</var>, <var data-var='time'>19:21</var> UTC Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

Elevated Errors Creating New Deployments

May <var data-var='date'>28</var>, <var data-var='time'>16:59</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>28</var>, <var data-var='time'>16:37</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>28</var>, <var data-var='time'>16:18</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>28</var>, <var data-var='time'>16:00</var> 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.

Elevated Function Invocation Errors in Stockholm region (ARN1)

May <var data-var='date'>27</var>, <var data-var='time'>05:02</var> 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 <var data-var='date'>27</var>, <var data-var='time'>04:50</var> UTC Investigating - We are currently investigating this issue.

Elevated Errors on Vercel Dashboard (Project Overview Page)

May <var data-var='date'>25</var>, <var data-var='time'>16:22</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>25</var>, <var data-var='time'>16:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>25</var>, <var data-var='time'>15:25</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>25</var>, <var data-var='time'>14:58</var> UTC Investigating - We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.

Delays Loading Runtime Logs

May <var data-var='date'>23</var>, <var data-var='time'>18:44</var> 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 <var data-var='date'>23</var>, <var data-var='time'>18:21</var> UTC Monitoring - GitHub has implemented a fix, and we are monitoring the results. May <var data-var='date'>23</var>, <var data-var='time'>15:46</var> UTC Identified - We have identified the issue and are working closely with GitHub to resolve it. May <var data-var='date'>23</var>, <var data-var='time'>14:30</var> UTC Update - We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops. May <var data-var='date'>23</var>, <var data-var='time'>12:15</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'>23</var>, <var data-var='time'>11:09</var> UTC Update - We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs. CLI deployments are unaffected at this time. May <var data-var='date'>23</var>, <var data-var='time'>10:43</var> UTC Investigating - We are currently investigating this issue.

Elevated Build Failures (GitHub connected projects)

May <var data-var='date'>22</var>, <var data-var='time'>17:11</var> 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.

Build Failures for Some Next.js Deployments

May <var data-var='date'>21</var>, <var data-var='time'>21:31</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>21</var>, <var data-var='time'>21:20</var> UTC Monitoring - The mitigation was successfully rolled out, and builds are stable. May <var data-var='date'>21</var>, <var data-var='time'>19:55</var> UTC Update - The root cause has been identified and we are rolling out a mitigation. May <var data-var='date'>21</var>, <var data-var='time'>15:01</var> UTC Identified - We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.

Elevated Build Errors

May <var data-var='date'>21</var>, <var data-var='time'>06:08</var> 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 <var data-var='date'>20</var>, <var data-var='time'>20:07</var> UTC Monitoring - We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.

Missing Build CPU Minutes Usage Data

May <var data-var='date'>18</var>, <var data-var='time'>23:52</var> 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 fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours. May <var data-var='date'>18</var>, <var data-var='time'>22:19</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'>18</var>, <var data-var='time'>22:16</var> UTC Monitoring - A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor. May <var data-var='date'>18</var>, <var data-var='time'>22:11</var> UTC Update - We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover. May <var data-var='date'>18</var>, <var data-var='time'>21:53</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>18</var>, <var data-var='time'>21:42</var> UTC Investigating - We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.

Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND

May <var data-var='date'>18</var>, <var data-var='time'>15:41</var> UTC Resolved - The incident is resolved and support cases can be submitted again. May <var data-var='date'>18</var>, <var data-var='time'>15:17</var> UTC Monitoring - We have implemented a fix. New support cases can be created. We continue to monitor. May <var data-var='date'>18</var>, <var data-var='time'>15:00</var> UTC Investigating - We are investigating an issue where support cannot be submitted through the dashboard.

Support cases cannot be submitted

May <var data-var='date'>15</var>, <var data-var='time'>16:18</var> UTC Resolved - The usage tracking system is fully recovered. May <var data-var='date'>15</var>, <var data-var='time'>15:39</var> UTC Monitoring - The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor. May <var data-var='date'>15</var>, <var data-var='time'>13:40</var> UTC Update - We are continuing to work on the fix. Usage tracking for Workflow Storage remains paused. The incorrect calculations will not be charged. May <var data-var='date'>15</var>, <var data-var='time'>11:37</var> UTC Identified - The team has identified the source of the incorrect usage data calculations and has paused usage tracking while a fix is being prepared. May <var data-var='date'>15</var>, <var data-var='time'>10:34</var> UTC Investigating - Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.

Workflow usage amounts are incorrectly calculated

May <var data-var='date'> 9</var>, <var data-var='time'>05:40</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 9</var>, <var data-var='time'>04:45</var> UTC Monitoring - Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.

Vercel Queues, and Vercel Workflow runs were delayed

May <var data-var='date'> 8</var>, <var data-var='time'>19:15</var> UTC Resolved - Between 18:36 and 19:04 UTC, issuing SSL certificates was delayed for new domains. These certificates have now been issued. Certificate renewals were not affected.

SSL Certificate Generation Delays

May <var data-var='date'> 8</var>, <var data-var='time'>16:41</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>16:33</var> UTC Monitoring - We have applied a fix and are observing recovery across all builds. We'll provide additional updates as-needed. May <var data-var='date'> 8</var>, <var data-var='time'>16:30</var> UTC Identified - We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they become available.

Delays Processing Builds

May <var data-var='date'> 8</var>, <var data-var='time'>06:39</var> UTC Resolved - We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region. May <var data-var='date'> 8</var>, <var data-var='time'>04:54</var> UTC Monitoring - We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours. May <var data-var='date'> 8</var>, <var data-var='time'>02:33</var> UTC Update - New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated. May <var data-var='date'> 8</var>, <var data-var='time'>02:18</var> UTC Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 8</var>, <var data-var='time'>02:13</var> UTC Update - New messages to Vercel Workflows and Vercel Queues are being queued, but message processing is paused. Queued messages will be processed when service is restored. May <var data-var='date'> 8</var>, <var data-var='time'>01:47</var> UTC Update - Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1. May <var data-var='date'> 8</var>, <var data-var='time'>01:18</var> UTC Identified - Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.

Is Vercel down?

Vercel status is UP

Lastest published events

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

Increase in Workflow runs stuck in pending, failed

Intermittent Login Failures on Vercel Dashboard

Vercel Services, Components and Regions

Recent Vercel events

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

Increase in Workflow runs stuck in pending, failed

Intermittent Login Failures on Vercel Dashboard

Increase in Workflow runs stuck as pending

Degraded Domain Search in Vercel Dashboard

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

Get your FREE account now,
5 monitors included!

Is Vercel down?

Vercel status is UP

Lastest published events

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

Increase in Workflow runs stuck in pending, failed

Intermittent Login Failures on Vercel Dashboard

Vercel Services, Components and Regions

Recent Vercel events

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

Increase in Workflow runs stuck in pending, failed

Intermittent Login Failures on Vercel Dashboard

Increase in Workflow runs stuck as pending

Degraded Domain Search in Vercel Dashboard

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!