Oct <var data-var='date'> 6</var>, <var data-var='time'>09:36</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 6</var>, <var data-var='time'>09:31</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 6</var>, <var data-var='time'>09:27</var> UTC Update - We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available. Oct <var data-var='date'> 6</var>, <var data-var='time'>09:12</var> UTC Identified - We've identified an issue where some customers may experience elevated error rates with Sandbox in Paris, France (cdg1). We are currently investigating this issue. We will share updates as they become available.

Elevated Sandbox error rates in Paris (cdg1)

Sep <var data-var='date'>28</var>, <var data-var='time'>14:11</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>28</var>, <var data-var='time'>13:44</var> UTC Monitoring - A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.

Build failures and 500 errors for functions using Edge runtime

Sep <var data-var='date'>18</var>, <var data-var='time'>22:31</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>18</var>, <var data-var='time'>22:14</var> UTC Monitoring - We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor. Sep <var data-var='date'>18</var>, <var data-var='time'>21:36</var> UTC Investigating - We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.

Deployment stuck in initializing state

Sep <var data-var='date'>18</var>, <var data-var='time'>21:22</var> UTC Resolved - The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required. Sep <var data-var='date'>18</var>, <var data-var='time'>21:13</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>18</var>, <var data-var='time'>21:07</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>18</var>, <var data-var='time'>20:56</var> UTC Update - We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available. Sep <var data-var='date'>18</var>, <var data-var='time'>20:32</var> UTC Investigating - We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.

Elevated Errors Triggering Deployments

Sep <var data-var='date'>18</var>, <var data-var='time'>12:00</var> UTC Resolved - Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.

Elevated Vercel KMS and Connect Errors

Sep <var data-var='date'>17</var>, <var data-var='time'>07:11</var> UTC Resolved - Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.

Failures delivering Logs to Drains

Sep <var data-var='date'>16</var>, <var data-var='time'>14:00</var> UTC Resolved - Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.

Missing Web Analytics and Speed Insights data

Sep <var data-var='date'>16</var>, <var data-var='time'>03:21</var> UTC Resolved - Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.

Invoice Generation Paused

Sep <var data-var='date'>10</var>, <var data-var='time'>19:16</var> UTC Resolved - Connect and Passport have fully recovered. This incident has been resolved. Sep <var data-var='date'>10</var>, <var data-var='time'>18:13</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>10</var>, <var data-var='time'>17:42</var> UTC Investigating - We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.

Elevated error rate on Connect and Passport

Sep <var data-var='date'> 4</var>, <var data-var='time'>20:27</var> UTC Resolved - Blob has fully recovered. This incident has been resolved. Sep <var data-var='date'> 4</var>, <var data-var='time'>20:19</var> UTC Update - Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly. Sep <var data-var='date'> 4</var>, <var data-var='time'>20:05</var> UTC Monitoring - The fix has been rolled out and we are seeing signs of recovery. Sep <var data-var='date'> 4</var>, <var data-var='time'>19:55</var> UTC Update - The fix is currently being rolled out. We'll provide another update once the rollout is complete and we're beginning to see signs of recovery. Sep <var data-var='date'> 4</var>, <var data-var='time'>19:33</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'> 4</var>, <var data-var='time'>19:33</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'> 4</var>, <var data-var='time'>19:11</var> UTC Investigating - We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.

Elevated latency in VCR, Blob, and Sandbox API

Sep <var data-var='date'> 1</var>, <var data-var='time'>20:58</var> UTC Resolved - This incident has been resolved. Builds have recovered. Sep <var data-var='date'> 1</var>, <var data-var='time'>20:49</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'> 1</var>, <var data-var='time'>20:45</var> UTC Monitoring - We are seeing recovery in Builds and are continuing to monitor. Sep <var data-var='date'> 1</var>, <var data-var='time'>20:37</var> UTC Identified - We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available. Sep <var data-var='date'> 1</var>, <var data-var='time'>20:27</var> UTC Update - We are actively working to fix an issue causing some deployments that use IAD1 Function regions or Routing Middleware to fail. We will provide additional updates as they become available. Sep <var data-var='date'> 1</var>, <var data-var='time'>19:59</var> UTC Investigating - We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.

Increased deployment failures

Aug <var data-var='date'>26</var>, <var data-var='time'>04:28</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>26</var>, <var data-var='time'>04:28</var> UTC Identified - The team has identified the source of the issue and is testing a fix. Aug <var data-var='date'>26</var>, <var data-var='time'>03:15</var> UTC Update - We are investigating errors logging in with Vercel CLI (vc login). Aug <var data-var='date'>26</var>, <var data-var='time'>03:06</var> UTC Investigating - We are investigating errors logging in with Vercel CLI (vc login).

Failures logging in with Vercel CLI

Aug <var data-var='date'>25</var>, <var data-var='time'>20:05</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>25</var>, <var data-var='time'>19:57</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>25</var>, <var data-var='time'>19:37</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>25</var>, <var data-var='time'>19:27</var> UTC Investigating - We're investigating elevated initialization times for some builds. We will provide updates as we learn more.

Elevated build initialization times

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.

Is Vercel down?

Vercel status is UP

Lastest published events

Elevated Sandbox error rates in Paris (cdg1)

Build failures and 500 errors for functions using Edge runtime

Deployment stuck in initializing state

Vercel Services, Components and Regions

Recent Vercel events

Elevated Sandbox error rates in Paris (cdg1)

Build failures and 500 errors for functions using Edge runtime

Deployment stuck in initializing state

Elevated Errors Triggering Deployments

Elevated Vercel KMS and Connect Errors

Failures delivering Logs to Drains