Aug <var data-var='date'>20</var>, <var data-var='time'>18:34</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>18:23</var> UTC Monitoring - We have deployed a fix. Newly deployed container functions are working as expected. Aug <var data-var='date'>20</var>, <var data-var='time'>17:46</var> UTC Identified - We've identified an issue where newly deployed container functions may return 5XX errors. Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.

New container functions are failing

Aug <var data-var='date'>20</var>, <var data-var='time'>11:25</var> UTC Resolved - The system is operating normally and fully recovered. Aug <var data-var='date'>20</var>, <var data-var='time'>11:21</var> UTC Monitoring - We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor. Aug <var data-var='date'>20</var>, <var data-var='time'>11:14</var> UTC Investigating - We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.

Logs unavailable to query in Dashboard

Aug <var data-var='date'>18</var>, <var data-var='time'>23:00</var> UTC Resolved - From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.

Elevated errors for Workflow streams

Aug <var data-var='date'>17</var>, <var data-var='time'>21:25</var> UTC Resolved - Services have recovered. We are still working to ingest missing observability data during this period. Aug <var data-var='date'>17</var>, <var data-var='time'>20:13</var> UTC Update - Services have recovered. We are still working to ingest missing observability data during this period. Aug <var data-var='date'>17</var>, <var data-var='time'>17:51</var> UTC Update - Login with TOTP has completely recovered. We are still working to ingest missing observability data during this period. We will share more information as it becomes available. Aug <var data-var='date'>17</var>, <var data-var='time'>16:46</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>17</var>, <var data-var='time'>16:44</var> UTC Monitoring - We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available. Aug <var data-var='date'>17</var>, <var data-var='time'>16:06</var> UTC Update - We are also investigating an issue where some customers may be unable to sign in to Dashboard with time-based one-time passwords (TOTP). We will share updates as they become available. Aug <var data-var='date'>17</var>, <var data-var='time'>15:09</var> UTC Update - We are continuing to investigate this issue. We will share updates as they become available. Aug <var data-var='date'>17</var>, <var data-var='time'>14:30</var> UTC Investigating - We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.

Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard

Aug <var data-var='date'>14</var>, <var data-var='time'>13:08</var> UTC Resolved - This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts. Deployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this period were not affected. If your project matches the conditions above and you deployed during the impact window, redeploy your project. Affected deployments are not fixed automatically; a new deployment is required to restore the affected routes.

Dynamic API routes returned 404 errors for some deployments

Aug <var data-var='date'> 6</var>, <var data-var='time'>18:29</var> UTC Resolved - This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed. Aug <var data-var='date'> 6</var>, <var data-var='time'>18:19</var> UTC Monitoring - Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:48</var> UTC Update - We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:06</var> UTC Identified - We've identified the issue and are working on a fix. We will provide updates as they become available. Aug <var data-var='date'> 6</var>, <var data-var='time'>16:58</var> UTC Update - We continue to investigate this issue and will provide updates as they become available. Aug <var data-var='date'> 6</var>, <var data-var='time'>16:37</var> UTC Investigating - We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.

Delays delivering log drains

Jul <var data-var='date'>26</var>, <var data-var='time'>17:46</var> UTC Resolved - Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience. Jul <var data-var='date'>25</var>, <var data-var='time'>18:57</var> UTC Investigating - The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.

Vercel Community temporarily unavailable

Jul <var data-var='date'>23</var>, <var data-var='time'>19:00</var> UTC Resolved - Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.

Telemetry data loss for Drains

Jul <var data-var='date'>23</var>, <var data-var='time'>08:18</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>07:55</var> UTC Monitoring - The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor. Jul <var data-var='date'>23</var>, <var data-var='time'>07:33</var> UTC Investigating - We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.

Timeouts loading charts and observability data in Dashboard

Jul <var data-var='date'>23</var>, <var data-var='time'>07:41</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>07:08</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>23</var>, <var data-var='time'>06:47</var> UTC Investigating - We are investigating an issue causing the dashboard to be inaccessible for some users.

Dashboard authentication errors

Jul <var data-var='date'>17</var>, <var data-var='time'>15:19</var> UTC Resolved - This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected. Jul <var data-var='date'>17</var>, <var data-var='time'>14:27</var> UTC Monitoring - We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment. Jul <var data-var='date'>17</var>, <var data-var='time'>14:19</var> UTC Identified - We have identified the source of errors and are implementing a fix. Jul <var data-var='date'>17</var>, <var data-var='time'>14:12</var> UTC Investigating - There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.

Increased invocation failures for Hobby Team functions

Jul <var data-var='date'>17</var>, <var data-var='time'>00:42</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>17</var>, <var data-var='time'>00:07</var> UTC Monitoring - Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered. Jul <var data-var='date'>16</var>, <var data-var='time'>23:39</var> UTC Identified - We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available. Jul <var data-var='date'>16</var>, <var data-var='time'>23:09</var> UTC Investigating - We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.

GitHub-linked deployments and authentication affected

Jul <var data-var='date'>16</var>, <var data-var='time'>10:45</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>16</var>, <var data-var='time'>10:23</var> UTC Monitoring - The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor. Jul <var data-var='date'>16</var>, <var data-var='time'>08:39</var> UTC Investigating - We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.

SAML Single Sign-On (SSO) errors

Jul <var data-var='date'>16</var>, <var data-var='time'>09:27</var> UTC Resolved - The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard. Jul <var data-var='date'>16</var>, <var data-var='time'>06: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

Jul <var data-var='date'>15</var>, <var data-var='time'>23:34</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>23:16</var> UTC Monitoring - A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available. Jul <var data-var='date'>15</var>, <var data-var='time'>23:04</var> UTC Identified - We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.

Errors accessing teams that require 2FA

Jul <var data-var='date'>10</var>, <var data-var='time'>23:28</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>10</var>, <var data-var='time'>21:22</var> 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 available. Failed deployments can be retried and should succeed.

Increased Build failure rates

Jul <var data-var='date'>10</var>, <var data-var='time'>22:36</var> UTC Resolved - We have unpaused all impacted deployments. We will continue to monitor the situation. Jul <var data-var='date'>10</var>, <var data-var='time'>21:32</var> 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 updates as they become available. Jul <var data-var='date'>10</var>, <var data-var='time'>20:50</var> UTC Update - We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner. Jul <var data-var='date'>10</var>, <var data-var='time'>19:53</var> UTC Identified - We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result. Jul <var data-var='date'>10</var>, <var data-var='time'>19:15</var> UTC Investigating - We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.

Erroneous budget notifications

Jul <var data-var='date'> 9</var>, <var data-var='time'>13:16</var> 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 loading Build Logs

Jul <var data-var='date'> 8</var>, <var data-var='time'>19:13</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 8</var>, <var data-var='time'>19:13</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>19:13</var> UTC Monitoring - Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available. Jul <var data-var='date'> 8</var>, <var data-var='time'>18:40</var> UTC Update - We are seeing signs of recovery and the affected build queue has started to drain. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. Jul <var data-var='date'> 8</var>, <var data-var='time'>18:05</var> UTC Investigating - We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.

Delays Processing Builds

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.

Is Vercel down?

Vercel status is UP

Lastest published events

New container functions are failing

Logs unavailable to query in Dashboard

Elevated errors for Workflow streams

Vercel Services, Components and Regions

Recent Vercel events

New container functions are failing

Logs unavailable to query in Dashboard

Elevated errors for Workflow streams

Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard

Dynamic API routes returned 404 errors for some deployments

Delays delivering log drains