Vercel Outage History

Vercel is up right now

Pingoru has recorded 125 incidents for Vercel: 125 in the last 12 months and 22 in the last 90 days.

Source: vercel-status.com

125incidents recorded
125last 12 months
22last 90 days
6 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Vercel in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261841 of 720 (6%)
May 20261952 of 744 (7%)
June 2026917 of 720 (2%)
July 20261417 of 744 (2%)
August 2026812 of 744 (2%)
September 2026108 of 720 (1%)
October 2026510 of 744 (1%)
November 202600 of 107 (0%)

Incidents, newest first

Minor October 23, 2026 Delays in Logs and Observability data 1h 1m Logs, Observability

Started Oct 23, 2026, 04:31 PM UTC· resolved Oct 23, 2026, 05:32 PM UTC

  1. identified Oct 23, 2026, 04:31 PM UTC

    We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.

  2. resolved Oct 23, 2026, 05:32 PM UTC

    The issue causing delays in Logs and Observability data has been resolved.

Read the full incident report →

Major October 12, 2026 Increased build and deployment failures 6h 36m Builds, Git Integrations

Started Oct 12, 2026, 01:35 PM UTC· resolved Oct 12, 2026, 08:11 PM UTC

  1. investigating Oct 12, 2026, 01:35 PM 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 Oct 12, 2026, 02:08 PM UTC

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

  3. identified Oct 12, 2026, 02:57 PM 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 Oct 12, 2026, 04:10 PM 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 Oct 12, 2026, 06:33 PM 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 Oct 12, 2026, 07:56 PM UTC

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

  7. resolved Oct 12, 2026, 08:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 10, 2026 Delays in Drains, Observability, and Workflow in Washington (iad1) 1h 21m Logs, Drains, Queues, Workflow and 1 more

Started Oct 10, 2026, 12:15 AM UTC· resolved Oct 10, 2026, 01:37 AM UTC

  1. investigating Oct 10, 2026, 12:15 AM 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 Oct 10, 2026, 12:35 AM 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 Oct 10, 2026, 01:12 AM 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 Oct 10, 2026, 01:37 AM UTC

    All services have recovered.

Read the full incident report →

Major October 6, 2026 Vercel Auth login failures for pages with Deployment Protection enabled 15m Routing Middleware

Started Oct 06, 2026, 04:10 PM UTC· resolved Oct 06, 2026, 04:26 PM UTC

  1. investigating Oct 06, 2026, 04:10 PM 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 Oct 06, 2026, 04:14 PM UTC

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

  3. monitoring Oct 06, 2026, 04:17 PM UTC

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

  4. resolved Oct 06, 2026, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 6, 2026 Elevated Sandbox error rates in Paris (cdg1) 24m Sandbox

Started Oct 06, 2026, 09:12 AM UTC· resolved Oct 06, 2026, 09:36 AM UTC

  1. identified Oct 06, 2026, 09:12 AM 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 Oct 06, 2026, 09:27 AM UTC

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

  3. monitoring Oct 06, 2026, 09:31 AM UTC

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

  4. resolved Oct 06, 2026, 09:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 28, 2026 Build failures and 500 errors for functions using Edge runtime 26m Builds

Started Sep 28, 2026, 01:44 PM UTC· resolved Sep 28, 2026, 02:11 PM UTC

  1. monitoring Sep 28, 2026, 01:44 PM 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 functions using Edge runtime to accelerate remediation.

  2. resolved Sep 28, 2026, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 18, 2026 Deployment stuck in initializing state 55m Builds

Started Sep 18, 2026, 09:36 PM UTC· resolved Sep 18, 2026, 10:31 PM UTC

  1. investigating Sep 18, 2026, 09:36 PM 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 Sep 18, 2026, 10:14 PM 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 Sep 18, 2026, 10:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 18, 2026 Elevated Errors Triggering Deployments 49m Builds

Started Sep 18, 2026, 08:32 PM UTC· resolved Sep 18, 2026, 09:22 PM UTC

  1. investigating Sep 18, 2026, 08:32 PM UTC

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

  2. investigating Sep 18, 2026, 08:56 PM UTC

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

  3. identified Sep 18, 2026, 09:07 PM UTC

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

  4. monitoring Sep 18, 2026, 09:13 PM UTC

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

  5. resolved Sep 18, 2026, 09:22 PM UTC

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

Read the full incident report →

Notice September 18, 2026 Elevated Vercel KMS and Connect Errors –

Started Sep 18, 2026, 12:00 PM UTC· resolved Sep 18, 2026, 12:00 PM UTC

  1. resolved Sep 18, 2026, 12:00 PM 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.

Read the full incident report →

Minor September 16, 2026 Missing Web Analytics and Speed Insights data 1h 40m

Started Sep 16, 2026, 02:00 PM UTC· resolved Sep 16, 2026, 03:40 PM UTC

  1. resolved Sep 16, 2026, 02:00 PM 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 are required.

Read the full incident report →

Notice September 16, 2026 Failures delivering Logs to Drains 20h 5m

Started Sep 16, 2026, 11:06 AM UTC· resolved Sep 17, 2026, 07:11 AM UTC

  1. resolved Sep 17, 2026, 07:11 AM 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 smaller payloads before delivery. Affected Drains data could not be redelivered.

Read the full incident report →

Notice September 16, 2026 Invoice Generation Paused –

Started Sep 16, 2026, 03:21 AM UTC· resolved Sep 16, 2026, 03:21 AM UTC

  1. resolved Sep 16, 2026, 03:21 AM 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 required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.

Read the full incident report →

Major September 10, 2026 Elevated error rate on Connect and Passport 1h 33m

Started Sep 10, 2026, 05:42 PM UTC· resolved Sep 10, 2026, 07:16 PM UTC

  1. investigating Sep 10, 2026, 05:42 PM 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 Sep 10, 2026, 06:13 PM UTC

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

  3. resolved Sep 10, 2026, 07:16 PM UTC

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

Read the full incident report →

Minor September 4, 2026 Elevated latency in VCR, Blob, and Sandbox API 1h 15m Blob, Sandbox

Started Sep 04, 2026, 07:11 PM UTC· resolved Sep 04, 2026, 08:27 PM UTC

  1. investigating Sep 04, 2026, 07:11 PM 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 Sep 04, 2026, 07:33 PM UTC

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

  3. identified Sep 04, 2026, 07:33 PM UTC

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

  4. identified Sep 04, 2026, 07:55 PM 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 Sep 04, 2026, 08:05 PM UTC

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

  6. monitoring Sep 04, 2026, 08:19 PM 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 Sep 04, 2026, 08:27 PM UTC

    Blob has fully recovered. This incident has been resolved.

Read the full incident report →

Major September 1, 2026 Increased deployment failures 59m Builds

Started Sep 01, 2026, 07:59 PM UTC· resolved Sep 01, 2026, 08:58 PM UTC

  1. investigating Sep 01, 2026, 07:59 PM 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 Sep 01, 2026, 08:27 PM 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 Sep 01, 2026, 08:37 PM 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 Sep 01, 2026, 08:45 PM UTC

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

  5. monitoring Sep 01, 2026, 08:49 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Sep 01, 2026, 08:58 PM UTC

    This incident has been resolved. Builds have recovered.

Read the full incident report →

Major August 26, 2026 Failures logging in with Vercel CLI 1h 22m Dashboard

Started Aug 26, 2026, 03:06 AM UTC· resolved Aug 26, 2026, 04:28 AM UTC

  1. investigating Aug 26, 2026, 03:06 AM UTC

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

  2. investigating Aug 26, 2026, 03:15 AM UTC

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

  3. identified Aug 26, 2026, 04:28 AM UTC

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

  4. resolved Aug 26, 2026, 04:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026 Elevated build initialization times 37m Builds

Started Aug 25, 2026, 07:27 PM UTC· resolved Aug 25, 2026, 08:05 PM UTC

  1. investigating Aug 25, 2026, 07:27 PM UTC

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

  2. identified Aug 25, 2026, 07:37 PM UTC

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

  3. monitoring Aug 25, 2026, 07:57 PM UTC

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

  4. resolved Aug 25, 2026, 08:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2026 New container functions are failing 47m Functions

Started Aug 20, 2026, 05:46 PM UTC· resolved Aug 20, 2026, 06:34 PM UTC

  1. identified Aug 20, 2026, 05:46 PM 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 Aug 20, 2026, 06:23 PM UTC

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

  3. resolved Aug 20, 2026, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2026 Logs unavailable to query in Dashboard 11m Logs

Started Aug 20, 2026, 11:14 AM UTC· resolved Aug 20, 2026, 11:25 AM UTC

  1. investigating Aug 20, 2026, 11:14 AM UTC

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

  2. monitoring Aug 20, 2026, 11:21 AM 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 Aug 20, 2026, 11:25 AM UTC

    The system is operating normally and fully recovered.

Read the full incident report →

Notice August 18, 2026 Elevated errors for Workflow streams 46m

Started Aug 18, 2026, 10:57 PM UTC· resolved Aug 18, 2026, 11:43 PM UTC

  1. resolved Aug 18, 2026, 11:00 PM 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.

Read the full incident report →

Minor August 17, 2026 Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard 6h 54m Dashboard, Firewall, Speed Insights, Web Analytics and 1 more

Started Aug 17, 2026, 02:30 PM UTC· resolved Aug 17, 2026, 09:25 PM UTC

  1. investigating Aug 17, 2026, 02:30 PM 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 Aug 17, 2026, 03:09 PM UTC

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

  3. investigating Aug 17, 2026, 04:06 PM 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 Aug 17, 2026, 04:44 PM 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 Aug 17, 2026, 04:46 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Aug 17, 2026, 05:51 PM 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 Aug 17, 2026, 08:13 PM UTC

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

  8. resolved Aug 17, 2026, 09:25 PM UTC

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

Read the full incident report →

Notice August 12, 2026 Dynamic API routes returned 404 errors for some deployments 1d 3h Builds

Started Aug 12, 2026, 05:12 PM UTC· resolved Aug 13, 2026, 08:33 PM UTC

  1. resolved Aug 14, 2026, 01:08 PM 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 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.

Read the full incident report →

Minor August 6, 2026 Delays delivering log drains 1h 52m Drains

Started Aug 06, 2026, 04:37 PM UTC· resolved Aug 06, 2026, 06:29 PM UTC

  1. investigating Aug 06, 2026, 04:37 PM 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 Aug 06, 2026, 04:58 PM UTC

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

  3. identified Aug 06, 2026, 05:06 PM UTC

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

  4. identified Aug 06, 2026, 05:48 PM UTC

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

  5. monitoring Aug 06, 2026, 06:19 PM UTC

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

  6. resolved Aug 06, 2026, 06:29 PM UTC

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

Read the full incident report →

Major July 23, 2026 Telemetry data loss for Drains 6m

Started Jul 23, 2026, 07:12 PM UTC· resolved Jul 23, 2026, 07:18 PM UTC

  1. resolved Jul 23, 2026, 07:00 PM 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 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.

Read the full incident report →

Major July 23, 2026 Timeouts loading charts and observability data in Dashboard 45m Firewall, Sandbox, Speed Insights, Web Analytics and 2 more

Started Jul 23, 2026, 07:33 AM UTC· resolved Jul 23, 2026, 08:18 AM UTC

  1. investigating Jul 23, 2026, 07:33 AM 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 Jul 23, 2026, 07:55 AM 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 Jul 23, 2026, 08:18 AM UTC

    This incident has been resolved.

Read the full incident report →