Vercel

Affected: Builds, Git Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

Started during GitHub: Incident with Actions, Pull Requests and Issues.

1. investigating 2026-10-12 13:35 UTC

   We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.

2. identified 2026-10-12 14:08 UTC

   We have identified the issue and are working on a fix. We will provide additional updates as they become available.

3. identified 2026-10-12 14:57 UTC

   Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.

4. identified 2026-10-12 16:10 UTC

   We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.

5. identified 2026-10-12 18:33 UTC

   Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.

6. monitoring 2026-10-12 19:56 UTC

   The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.

7. resolved 2026-10-12 20:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Drains, Logs, Observability, Queues, Workflow

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-10 00:15 UTC

   We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.

2. identified 2026-10-10 00:35 UTC

   A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.

3. monitoring 2026-10-10 01:12 UTC

   Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available.

4. resolved 2026-10-10 01:37 UTC

   All services have recovered.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Routing Middleware

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 16:10 UTC

   We are investigating an issue causing Vercel Auth login failures for pages with Deployment Protection enabled. We will provide an update as more information becomes available.

2. identified 2026-10-06 16:14 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-06 16:17 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-06 16:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Sandbox

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-10-06 09:12 UTC

   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.

2. identified 2026-10-06 09:27 UTC

   We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.

3. monitoring 2026-10-06 09:31 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-06 09:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. monitoring 2026-09-28 13:44 UTC

   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...

2. resolved 2026-09-28 14:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-18 21:36 UTC

   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.

2. monitoring 2026-09-18 22:14 UTC

   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.

3. resolved 2026-09-18 22:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-18 20:32 UTC

   We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.

2. investigating 2026-09-18 20:56 UTC

   We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.

3. identified 2026-09-18 21:07 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-09-18 21:13 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-09-18 21:22 UTC

   The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-18 12:00 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-17 07:11 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-16 14:00 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-16 03:21 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-10 17:42 UTC

   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.

2. identified 2026-09-10 18:13 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-09-10 19:16 UTC

   Connect and Passport have fully recovered. This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Blob, Sandbox

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-04 19:11 UTC

   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.

2. identified 2026-09-04 19:33 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-09-04 19:33 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-09-04 19:55 UTC

   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.

5. monitoring 2026-09-04 20:05 UTC

   The fix has been rolled out and we are seeing signs of recovery.

6. monitoring 2026-09-04 20:19 UTC

   Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.

7. resolved 2026-09-04 20:27 UTC

   Blob has fully recovered. This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-01 19:59 UTC

   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.

2. investigating 2026-09-01 20:27 UTC

   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.

3. identified 2026-09-01 20:37 UTC

   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.

4. monitoring 2026-09-01 20:45 UTC

   We are seeing recovery in Builds and are continuing to monitor.

5. monitoring 2026-09-01 20:49 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-09-01 20:58 UTC

   This incident has been resolved. Builds have recovered.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-26 03:06 UTC

   We are investigating errors logging in with Vercel CLI (vc login).

2. investigating 2026-08-26 03:15 UTC

   We are investigating errors logging in with Vercel CLI (vc login).

3. identified 2026-08-26 04:28 UTC

   The team has identified the source of the issue and is testing a fix.

4. resolved 2026-08-26 04:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-25 19:27 UTC

   We're investigating elevated initialization times for some builds. We will provide updates as we learn more.

2. identified 2026-08-25 19:37 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-25 19:57 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-25 20:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Functions

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-08-20 17:46 UTC

   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.

2. monitoring 2026-08-20 18:23 UTC

   We have deployed a fix. Newly deployed container functions are working as expected.

3. resolved 2026-08-20 18:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-20 11:14 UTC

   We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.

2. monitoring 2026-08-20 11:21 UTC

   We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.

3. resolved 2026-08-20 11:25 UTC

   The system is operating normally and fully recovered.

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-18 23:00 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, Observability, Speed Insights, Web Analytics, Firewall

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-17 14:30 UTC

   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.

2. investigating 2026-08-17 15:09 UTC

   We are continuing to investigate this issue. We will share updates as they become available.

3. investigating 2026-08-17 16:06 UTC

   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.

4. monitoring 2026-08-17 16:44 UTC

   We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available.

5. monitoring 2026-08-17 16:46 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2026-08-17 17:51 UTC

   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.

7. monitoring 2026-08-17 20:13 UTC

   Services have recovered. We are still working to ingest missing observability data during this period.

8. resolved 2026-08-17 21:25 UTC

   Services have recovered. We are still working to ingest missing observability data during this period.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-14 13:08 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Drains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-06 16:37 UTC

   We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.

2. investigating 2026-08-06 16:58 UTC

   We continue to investigate this issue and will provide updates as they become available.

3. identified 2026-08-06 17:06 UTC

   We've identified the issue and are working on a fix. We will provide updates as they become available.

4. identified 2026-08-06 17:48 UTC

   We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.

5. monitoring 2026-08-06 18:19 UTC

   Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.

6. resolved 2026-08-06 18:29 UTC

   This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-23 19:00 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Observability, Speed Insights, Web Analytics, Firewall, Sandbox, Workflow

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-07-23 07:33 UTC

   We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.

2. monitoring 2026-07-23 07:55 UTC

   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.

3. resolved 2026-07-23 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-07-23 06:47 UTC

   We are investigating an issue causing the dashboard to be inaccessible for some users.

2. monitoring 2026-07-23 07:08 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-23 07:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Functions

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-07-17 14:12 UTC

   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.

2. identified 2026-07-17 14:19 UTC

   We have identified the source of errors and are implementing a fix.

3. monitoring 2026-07-17 14:27 UTC

   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.

4. resolved 2026-07-17 15:19 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, Builds, Git Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

Started during GitHub: Degraded REST API Availability.

1. investigating 2026-07-16 23:09 UTC

   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.

2. identified 2026-07-16 23:39 UTC

   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.

3. monitoring 2026-07-17 00:07 UTC

   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,...

4. resolved 2026-07-17 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: SAML Single Sign-On

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-07-16 08:39 UTC

   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.

2. monitoring 2026-07-16 10:23 UTC

   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...

3. resolved 2026-07-16 10:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. monitoring 2026-07-16 06:07 UTC

   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.

2. resolved 2026-07-16 09:27 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, AI Gateway, API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-07-15 23:04 UTC

   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.

2. monitoring 2026-07-15 23:16 UTC

   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.

3. resolved 2026-07-15 23:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. monitoring 2026-07-10 21:22 UTC

   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.

2. resolved 2026-07-10 23:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, Builds

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-07-10 19:15 UTC

   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...

2. identified 2026-07-10 19:53 UTC

   We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result.

3. identified 2026-07-10 20:50 UTC

   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.

4. identified 2026-07-10 21:32 UTC

   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.

5. resolved 2026-07-10 22:36 UTC

   We have unpaused all impacted deployments. We will continue to monitor the situation.

Excerpts are shortened. Read the full incident on Vercel's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 13:16 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-07-08 18:05 UTC

   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.

2. investigating 2026-07-08 18:40 UTC

   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.

3. monitoring 2026-07-08 19:13 UTC

   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.

4. monitoring 2026-07-08 19:13 UTC

   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.

5. resolved 2026-07-08 19:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, CLE1 - Cleveland, East US, IAD1 - Washington DC, USA, Functions

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-07-02 16:31 UTC

   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.

2. identified 2026-07-02 16:33 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-02 16:39 UTC

   A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.

4. resolved 2026-07-02 16:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Workflow

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-07-01 16:57 UTC

   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...

2. identified 2026-07-01 17:49 UTC

   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.

3. resolved 2026-07-01 18:30 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-06-26 13:08 UTC

   We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.

2. investigating 2026-06-26 13:23 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-26 14:08 UTC

   We are continuing to investigate this issue and will provide an update as soon as we have more information.

4. identified 2026-06-26 14:11 UTC

   The issue has been identified and a fix is being implemented.

5. identified 2026-06-26 14:29 UTC

   Login is recovering for most users. We're monitoring to ensure stability.

6. monitoring 2026-06-26 15:03 UTC

   A fix has been implemented and we are monitoring the results.

7. resolved 2026-06-26 15:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Workflow

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-06-25 07:45 UTC

   We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.

2. identified 2026-06-25 08:27 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-06-25 09:25 UTC

   The issue has been identified. We are continuing to work on a fix for this issue.

4. identified 2026-06-25 10:42 UTC

   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.

5. identified 2026-06-25 12:15 UTC

   We are currently rolling a fix for the issue. We are monitoring the results.

6. monitoring 2026-06-25 13:30 UTC

   The fix has been fully rolled out and we are monitoring the results.

7. resolved 2026-06-25 13:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Domain Registration

1. investigating 2026-06-23 23:24 UTC

   We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.

2. identified 2026-06-23 23:26 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-23 23:28 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-23 23:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Functions

1. resolved 2026-06-19 17:54 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard, Observability, Speed Insights, Web Analytics, Firewall

1. investigating 2026-06-16 13:39 UTC

   We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.

2. investigating 2026-06-16 14:45 UTC

   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.

3. identified 2026-06-16 15:16 UTC

   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.

4. monitoring 2026-06-16 15:26 UTC

   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.

5. resolved 2026-06-16 15:39 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: FRA1 - Frankfurt, Germany, Europe

1. investigating 2026-06-14 21:03 UTC

   We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.

2. identified 2026-06-14 21:07 UTC

   We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

3. identified 2026-06-14 21:26 UTC

   The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

4. identified 2026-06-14 23:15 UTC

   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.

5. monitoring 2026-06-15 00:25 UTC

   All traffic has been restored to the FRA1 Vercel Region.

6. resolved 2026-06-15 01:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

1. investigating 2026-06-09 14:09 UTC

   We are currently investigating this issue.

2. identified 2026-06-09 14:33 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-09 14:39 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-09 14:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Functions

1. identified 2026-06-08 18:57 UTC

   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.

2. identified 2026-06-08 19:04 UTC

   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...

3. monitoring 2026-06-08 19:36 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-06-08 19:36 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-08 20:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

1. investigating 2026-06-01 19:21 UTC

   We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

2. identified 2026-06-01 19:50 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-01 19:55 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-01 20:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Functions, Routing Middleware

1. investigating 2026-05-28 16:00 UTC

   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.

2. identified 2026-05-28 16:18 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-28 16:37 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-28 16:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Dashboard

1. investigating 2026-05-27 04:50 UTC

   We are currently investigating this issue.

2. resolved 2026-05-27 05:02 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Logs

1. investigating 2026-05-25 14:58 UTC

   We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.

2. identified 2026-05-25 15:25 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-25 16:05 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-25 16:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Affected: Builds

Names an upstream provider: GitHub.

1. investigating 2026-05-23 10:43 UTC

   We are currently investigating this issue.

2. investigating 2026-05-23 11:09 UTC

   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.

3. investigating 2026-05-23 12:15 UTC

   We are continuing to investigate this issue.

4. investigating 2026-05-23 14:30 UTC

   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.

5. identified 2026-05-23 15:46 UTC

   We have identified the issue and are working closely with GitHub to resolve it.

6. monitoring 2026-05-23 18:21 UTC

   GitHub has implemented a fix, and we are monitoring the results.

7. resolved 2026-05-23 18:44 UTC

   This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-22 17:11 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-21 21:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-21 06:08 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-18 23:52 UTC

   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...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-18 15:41 UTC

   The incident is resolved and support cases can be submitted again.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-15 16:18 UTC

   The usage tracking system is fully recovered.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-09 05:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-08 19:15 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-08 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-08 06:39 UTC

   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.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-07 21:48 UTC

   This issue has been resolved and new deployments are being created successfully.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-06 00:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-06 00:38 UTC

   All services remain operational. New data is being processed as expected. The majority of the backfill is complete and a long tail of data will be processed within the next couple of hours.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-04 21:30 UTC

   Between 21:45–21:52 UTC, some users may have experienced request failures in ICN1. The issue has been identified, a fix has been applied, and the issue has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-05-01 11:30 UTC

   Between May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content were unaffected this time. We have reverted the change that caused the issue...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-30 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-30 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-29 16:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-28 16:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-28 09:00 UTC

   We have identified an issue resulting in delayed and/or missing usage data for observability events between 9:00 - 10:30 UTC and 16:50 - 19:30 UTC. The issue has been identified and resolved. Usage data for observability events for the affected time buckets have been recovered....

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-25 04:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-22 23:00 UTC

   We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period. All...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-23 01:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-21 14:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-20 20:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-20 10:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-20 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-19 21:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-07 18:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-07 08:37 UTC

   The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-02 23:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-02 18:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-04-01 22:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-31 21:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-31 13:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-25 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-24 16:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-24 05:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-13 23:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

1. resolved 2026-03-12 01:15 UTC

   Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-06 21:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-06 21:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-03 21:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-16 18:44 UTC

   Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-02 12:08 UTC

   This incident was resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-02 15:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-03-02 00:22 UTC

   A fix has been implemented and new deployments are no longer failing.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-28 06:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-13 02:56 UTC

   The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-11 15:00 UTC

   On February 11, 2026, between 15:00 and 19:26 UTC, AI Gateway experienced elevated error rates due to an issue affecting Vercel Functions infrastructure in the cle1 and fra1 Vercel Regions. Requests routed to these regions, including requests originating from other regions, may...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-07 11:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-05 20:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-03 21:36 UTC

   The issue has been resolved and all deployments are building normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-03 21:54 UTC

   This issue has been resolved and sandboxes are creating normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-03 17:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-02-01 08:57 UTC

   There were elevated error rates in the sin1 (Singapore) edge region between 08:57 and 09:04 UTC. The issue has been resolved, and all systems are operating normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-01-30 11:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-01-28 20:21 UTC

   This incident has been resolved, and traffic has been fully routed back to the dub1 region.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-01-26 17:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-01-23 04:28 UTC

   After monitoring, we do not see the issue persisting. This incident is resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2026-01-14 10:50 UTC

   After monitoring our fix, we found no new occurrences of build errors. This issue has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-12 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-12 11:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-10 06:22 UTC

   Vercel API errors have been resolved and dashboard access is restored across all regions. Queued deployments are recovering automatically, but failed deployments may need to be redeployed manually.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-09 05:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-08 21:38 UTC

   We received reports of elevated errors loading Vercel Logs and Speed Insights at 21:15 UTC. A fix was released at 21:25 UTC, and full functionality was restored by 21:38 UTC.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-07 23:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-12-02 11:06 UTC

   The issue causing elevated error rates for Domain Registrations has been resolved. Domains are now successfully provisioned and available for immediate use. Some payment attempts may not have completed; we will automatically retry those payments later. No action is needed from...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-26 19:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-18 15:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-17 10:30 UTC

   Builds and deployments were stuck in a queued state between 10:05 to 10:30 UTC. Our team identified the root cause and deployed a fix, and everything is now operating normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-16 19:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-14 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-14 18:50 UTC

   A change was merged to the Vercel dashboard that introduced a bug in the query for runtime logs in some situations. Upon being alerted, the dashboard was rolled back, which restored the ability to see runtime logs. The change was then reverted. Data was still being collected and...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-11 19:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-04 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-11-04 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-30 18:00 UTC

   The issue has been fully mitigated, and this incident has been resolved. No action is needed for customers with queued builds.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-29 00:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-27 04:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-23 01:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-22 01:25 UTC

   The delay affecting data delivery to drains in the iad1 region has been resolved. All services are now operating normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-21 00:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-21 07:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-16 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-10 03:10 UTC

   The incident has been resolved, and sign in is possible again.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-10-05 10:00 UTC

   Some customers may have experienced delays in builds for deployments between 10:58 and 12:35 UTC. These deployments appeared as Queued within the incident window.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-23 16:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-23 16:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-17 14:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-10 04:00 UTC

   We investigated elevated reports of 5xx errors and latency in the gru1 (São Paulo, Brazil) region between Sep 10, 3:45 AM – Sep 10, 3:48 AM UTC. The issue has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-05 18:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-09-03 13:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-26 17:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-21 19:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-21 15:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-12 17:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-06 22:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-05 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-08-01 08:49 UTC

   This incident has been resolved. The issue originated from a disruption on GitLab’s side. For more information, please refer to their incident report: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20290

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-29 21:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-22 02:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-21 18:26 UTC

   We are no longer observing increased errors, and the incident should be resolved. Our team is still monitoring our health metrics closely.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-04 16:30 UTC

   The incident has been resolved. We are still monitoring the status of our build's systems, and related services, closely.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-03 15:46 UTC

   The incident was resolved. During this window (11:14 - 15:16 UTC, depending on regions), some request data, like external API calls, was not recorded due to an internal logging disruption. As a result, requests made during this period will not appear in the dashboard, logs, or...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-07-02 19:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-30 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

1. resolved 2025-06-27 23:13 UTC

   Between 22:58 and 23:33 UTC, an internal service degradation caused deployments triggered by GitHub to not be properly processed. Service has been fully restored, but impacted customers need to re-trigger deployments attempted during this interval.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-18 15:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-17 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-12 21:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-09 19:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-06 22:08 UTC

   From 19:27 to 20:40 UTC, the Observability tab showed wrong status codes and error rates for Edge Functions. We’re working on correcting this data, and the correction should be fully completed in the next 12 hours.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-06-05 03:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

Started during GitHub: We're experiencing errors.

1. resolved 2025-05-26 10:02 UTC

   All systems normal.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-23 19:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-16 19:57 UTC

   All domain verification functionality has been restored.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-15 19:49 UTC

   We have restored functionality to impacted services.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-15 09:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-05 14:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-05-01 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-28 13:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-24 17:04 UTC

   Some users may have experienced issues accessing v0 from 17:04 UTC - 17:10 UTC. This issue has since been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-18 16:00 UTC

   Some users may have experienced issues deploying from v0 if Radix tabs were used between 15:50 and 17:05 UTC. This issue is now fixed.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-15 07:40 UTC

   Between 07:40 and 07:58 UTC, some users experienced increased latency and error rates for traffic served through the hnd1 (Tokyo, Japan) region. The issue has been resolved, and services are now operating normally.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-11 15:17 UTC

   This issue is now resolved. nppmjs.org have marked the issue as resolved on their status page as of 15:00 UTC.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-10 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-10 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-08 20:23 UTC

   Access to the Vercel Community site has been restored. If you are still unable to reach the site, please try clearing your browser cache or opening in an Incognito/Private window.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-08 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-07 17:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-07 11:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-03 15:31 UTC

   The issue has now been fully resolved. From 12:15 UTC - 14:57 UTC, a portion of deployments on Enhanced Build Machines were delayed in a "Queued" state. No deployments were lost and all deployments are now building as expected.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-04-03 04:45 UTC

   Normal routing to our Washington D.C. iad1 region has been fully restored. The incident is now resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-30 09:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-23 12:47 UTC

   During a 4-minute window today between 12:47-12:51 UTC, we experienced a brief increase in 500 errors affecting a small subset of Edge Functions invocations. The issue was isolated to the following regions: lhr1, bom1, hkg1, cdg1, hdn1, iad1. Edge Middleware and Serverless...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-21 13:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-18 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-18 17:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-11 16:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-11 07:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-03-09 15:33 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-28 19:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-26 12:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-26 06:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-20 23:17 UTC

   The issue affecting the delivery of Vercel login verification emails to some Outlook / Microsoft Exchange users has been resolved. Our monitoring systems indicate that email deliverability has returned to normal levels. If you previously experienced delays, you may need to...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-14 06:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-13 02:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-11 18:24 UTC

   The queue has been fully processed and this incident is now resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

1. resolved 2025-02-11 12:40 UTC

   We experienced issues with email-based authentication from 11:15 to 12:40 UTC. During that time, users were not able to log in or sign up via email for both the Vercel platform and the v0 service. Logins or signups via GitHub, GitLab or Bitbucket were not impacted.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-10 15:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-07 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-07 21:24 UTC

   There were elevated error rates in the iad1 region from 20:54 UTC to 21:13 UTC. The issue is now resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-07 20:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-06 22:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-06 23:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-07 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-05 19:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-05 22:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-02-05 07:03 UTC

   Following a detailed investigation, we have confirmed that our Cron Jobs service and all other systems are operating as expected, and none of our customers are affected.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-30 20:30 UTC

   We have released a fix and the issue has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

Started during GitHub: Incident with Pull Requests and Issues.

1. resolved 2025-01-30 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-28 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-23 01:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-21 18:32 UTC

   Between 16:04 and 18:33 (UTC) on January 21st, a small subset of deployments created Serverless Functions in the sfo1 (San Francisco, USA/us-west-1) region instead of their specified region. All functions remained fully operational during this period, with some users...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-19 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-15 09:00 UTC

   We have identified and resolved an issue impacting a subset of customers in the In-Function Concurrency Beta program. This issue only affects projects deployed between 2025-01-15 09:27 UTC and 14:33 UTC with In-Function Concurrency (Beta) enabled. This issue solely impacts the...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-15 08:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-14 11:08 UTC

   The issue has been successfully resolved, and all Vercel dashboard functionalities have been fully restored.

Excerpts are shortened. Read the full incident on Vercel's status page.

Names an upstream provider: GitHub.

1. resolved 2025-01-13 23:00 UTC

   As a result of GitHub degradation, new Vercel deployments triggered from GitHub commits were delayed while the GitHub incident was active. Customers were still able to create deployments using the Vercel dashboard or the Vercel CLI. Builds created between 2025-01-13 23:36 UTC...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-11 01:30 UTC

   Our team identified an issue within the Domain settings interface that resulted in a "Failed to Load" error message. The issue was limited to the settings page and did not affect the functionality or performance of deployed websites, which remained fully operational. The root...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-09 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2025-01-08 17:58 UTC

   Due to a faulty build container update a small portion of builds failed to run correctly, causing builds to fail with the following message: "Error: It’s not possible to provide `stdio` in combination with one of `stdin`, `stdout`, `stderr`" or "Error: This deployment is no...

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-24 08:13 UTC

   The data cache was degraded for fra1 from 08:13 to 08:34 UTC and from 09:48 to 09:50 UTC on 2024-12-24. During this period, requests to the Vercel Data Cache were slower and could cause Functions executions to time out.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-17 10:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-16 18:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-13 11:32 UTC

   This incident has been resolved, all blob URLs are working as usual.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-12 14:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-05 19:57 UTC

   Elevated error rates for login and calls to Vercel API from 19:50 to 19:57 UTC

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-03 15:15 UTC

   On December 3rd from 13:49 - 14:46 UTC, we saw an increase in response time and 5xx errors from Edge Middleware/Functions in our fra1 (Frankfurt, Germany) region. This degradation has now been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-12-01 19:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-26 12:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-21 16:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-20 21:17 UTC

   From 21:17 to 21:46 UTC Monitoring and Firewall observability experienced a brief degradation, where the UI was unavailable. There was no data loss, and the issue has been mitigated.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-14 20:08 UTC

   This incident has been resolved. Some of the usage data between Nov 14, 15:12 pm – Nov 14, 19:16 pm UTC may still be delayed. However, we’re actively working on backfilling the data and expect them to be synced soon.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-13 14:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-09 00:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-08 23:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.

1. resolved 2024-11-07 18:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vercel's status page.