Hosting / Frontend cloud / Vercel

Vercel

OPERATIONAL

Since May 2026 · 50 incidents · www.vercel-status.com · checked just now

CompareStatus page
GradeCLast 90 days
BPRODBSHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
230 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
47m
LongestLongest single incident, start to resolved.
22h 49m
Since lastTime since the last counted incident was resolved.
9d 23h

By area

BProduction
8INCIDENTS
11h 13mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Sep 10, 2026 · 1h 34mElevated error rate on Connect and Passport
SEV 2Sep 4, 2026 · 1h 16mElevated latency in VCR, Blob, and Sandbox API
SEV 2Aug 20, 2026 · 47mNew container functions are failing
Most hit
Sandbox2
Routing Middleware1
Blob1
Storage - Blob1
Worse. 18 in the last 6 months, 0 in the 6 before.
BShipping
15INCIDENTS
23h 39mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Sep 1, 2026 · 59mIncreased deployment failures
SEV 2Sep 18, 2026 · 50mElevated Errors Triggering Deployments
SEV 3Aug 17, 2026 · 6h 55mPartial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard
Most hit
Builds7
Build & Deploy - Builds7
Drains2
Logs2
Worse. 28 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Pro, one seat5 of 8 cheaper · Heroku: cheaper, better grade
~$20/mo
Pro seat (includes $20 of usage)$20

Hobby is for personal, non-commercial use only. Assumes the workload fits Pro's included $20 usage credit; serverless, so memory isn't reserved. vercel.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 50 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down9
Sev 3 · Can't shipCan't deploy, build or manage it8
Sev 4 · PapercutDocs, status page, slow dashboard6

When it breaks

Start times, last 12 months, UTC.

What breaks

Builds15 incidents
Build & Deploy - Builds14 incidents
Dashboard10 incidents
Dashboard - Dashboard10 incidents
Functions6 incidents
Observability4 incidents

Communication

Updates eachStatus page updates per incident, on average.
3.7Last 12 months
Update gapMedian time between status page updates during an incident.
22mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 19Sev 1–2

Incident history

Oct 12, 20266h 36mSEV 3
Increased build and deployment failuresSome customers' builds failed or deployments did not start from about 13:35 to 20:11 UTC. Failure rates fell by 14:57 but queued builds stayed slow. GitHub-connected projects were still failing during a GitHub incident. Deployment status events were delayed, then the backlog was cleared. The provider's cause and fix were not detailed.AI-graded · some customers · Builds +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds had a partial outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Some builds and deployments failed or queued for hours, mainly GitHub-connected projects; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 13:35 UTC · investigating
    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. 14:08 UTC · identified
    We have identified the issue and are working on a fix. We will provide additional updates as they become available.
  3. 14:57 UTC · identified
    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. 16:10 UTC · identified
    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. 18:33 UTC · identified
    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. 19:56 UTC · monitoring
    The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
  7. 20:11 UTC · resolved
    This incident has been resolved.
Source
Oct 10, 20261h 21mSEV 3
Delays in Drains, Observability, and Workflow in Washington (iad1)Delayed drain deliveries, logs, metrics, traces and pending Workflow runs in Washington (iad1) from about 00:15 to 01:37 UTC. Some customers were affected. Delivery resumed after a fix at 00:35 and backlogs were processed by 01:12. Services were marked recovered at 01:37.AI-graded · one location · Drains +7
Why this grade
  1. RULES · SEV 1
    Sev 1 because Queues had a partial outage
  2. CLAUDE · SEV 3 · LOCAL · MEDIUM CONFIDENCE
    Drains, logs, observability and Workflow runs were delayed in one Washington (iad1) region for about 80 minutes; apps kept serving.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 00:15 UTC · investigating
    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. 00:35 UTC · identified
    A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.
  3. 01:12 UTC · monitoring
    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. 01:37 UTC · resolved
    All services have recovered.
Source
Oct 6, 202616mSEV 2
Vercel Auth login failures for pages with Deployment Protection enabledVercel Auth login failed for pages with Deployment Protection enabled starting 16:10 UTC on 2026-10-06. Affected component was Routing Middleware. A fix was implemented and the incident resolved at 16:26 UTC after about 16 minutes. The text gives no further cause detail.AI-graded · some customers · Routing Middleware
Why this grade
  1. RULES · SEV 1
    Sev 1 because Routing Middleware had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Vercel Auth login failed on pages with Deployment Protection for about 16 minutes; other pages were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 16:10 UTC · investigating
    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. 16:14 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:17 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 16:26 UTC · resolved
    This incident has been resolved.
Source
Oct 6, 202625mSEV 2
Elevated Sandbox error rates in Paris (cdg1)Vercel Sandbox in Paris (cdg1) had elevated error rates for some customers, starting 09:12 UTC and resolved by 09:36 UTC on 6 October 2026. The provider said a fix was implemented and monitored before resolution. No cause was given in the updates.AI-graded · regional · Sandbox
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Sandbox requests failed at elevated rates for some customers in the Paris (cdg1) region for about 25 minutes; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 09:12 UTC · identified
    We've identified an issue where some customers may experience elevated error rates with Sandbox in Paris, France (cdg1). We are currently investigating this issue. We will share updates as they become available.
  2. 09:27 UTC · identified
    We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.
  3. 09:31 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 09:36 UTC · resolved
    This incident has been resolved.
Source
Sep 28, 202627mSEV 3
Build failures and 500 errors for functions using Edge runtimeSev 3 because Builds had a partial outageBuilds +1
2 updates
  1. 13:44 UTC · monitoring
    A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.
  2. 14:11 UTC · resolved
    This incident has been resolved.
Source
Sep 18, 202655mSEV 3
Deployment stuck in initializing stateBuilds for an elevated share of deployments got stuck initializing for about 55 minutes; the text does not give the share.AI-graded · Builds +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Builds for an elevated share of deployments got stuck initializing for about 55 minutes; the text does not give the share.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 21:36 UTC · investigating
    We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.
  2. 22:14 UTC · monitoring
    We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.
  3. 22:31 UTC · resolved
    This incident has been resolved.
Source
Sep 18, 202650mSEV 2
Elevated Errors Triggering DeploymentsVercel saw elevated errors triggering deployments from about 20:32 to 21:22 UTC on 18 September 2026. It was identified, a fix was deployed, and it was resolved. Existing deployments and traffic were unaffected; no action was needed.AI-graded · Builds +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Elevated errors caused deployments to fail for about 50 minutes; existing deployments and traffic were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 20:32 UTC · investigating
    We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.
  2. 20:56 UTC · investigating
    We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.
  3. 21:07 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 21:13 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 21:22 UTC · resolved
    The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.
Source
Sep 18, 20260mSEV 2
Elevated Vercel KMS and Connect ErrorsSev 2 from the incident title (no components listed)
1 update
  1. 12:00 UTC · resolved
    Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.
Source
Sep 17, 20260mSEV 3
Failures delivering Logs to DrainsSev 3 from the incident title (no components listed)
1 update
  1. 07:11 UTC · resolved
    Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.
Source
Sep 16, 20260mSEV 4
Missing Web Analytics and Speed Insights dataSev 4 from the incident title (no components listed)
1 update
  1. 14:00 UTC · resolved
    Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.
Source
Sep 16, 20260mSEV 4
Invoice Generation PausedSev 4 from the incident title (no components listed)
1 update
  1. 03:21 UTC · resolved
    Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.
Source
Sep 10, 20261h 34mSEV 2
Elevated error rate on Connect and PassportConnect and Passport returned elevated errors for some customers for about 90 minutes; the text gives no further detail on scope.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · LOW CONFIDENCE
    Connect and Passport returned elevated errors for some customers for about 90 minutes; the text gives no further detail on scope.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 17:42 UTC · investigating
    We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.
  2. 18:13 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 19:16 UTC · resolved
    Connect and Passport have fully recovered. This incident has been resolved.
Source
Sep 4, 20261h 16mSEV 2
Elevated latency in VCR, Blob, and Sandbox APIVercel reported elevated latency for some customers on API requests to VCR, Blob and Sandbox from about 19:11 to 20:27 UTC on September 4. The cause was identified and a fix was rolled out. VCR and Sandbox recovered by 20:19 and Blob fully recovered by 20:27.AI-graded · Blob +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because Blob had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Some customers saw increased latency on Blob storage API requests for about 75 minutes; the scope across customers is not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 19:11 UTC · investigating
    We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.
  2. 19:33 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 19:33 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 19:55 UTC · identified
    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. 20:05 UTC · monitoring
    The fix has been rolled out and we are seeing signs of recovery.
  6. 20:19 UTC · monitoring
    Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.
  7. 20:27 UTC · resolved
    Blob has fully recovered. This incident has been resolved.
Source
Sep 1, 202659mSEV 2
Increased deployment failuresSome Vercel deployments that used IAD1 Function regions or Routing Middleware failed to build from about 19:59 to 20:58 UTC on September 1, 2026. The update text gives no cause; builds recovered after a fix was deployed.AI-graded · some customers · Builds +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · HIGH CONFIDENCE
    Some deployments using IAD1 Function regions or Routing Middleware failed to build for about an hour; other deployments were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 19:59 UTC · investigating
    We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.
  2. 20:27 UTC · investigating
    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. 20:37 UTC · identified
    We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available.
  4. 20:45 UTC · monitoring
    We are seeing recovery in Builds and are continuing to monitor.
  5. 20:49 UTC · monitoring
    We are continuing to monitor for any further issues.
  6. 20:58 UTC · resolved
    This incident has been resolved. Builds have recovered.
Source
Aug 26, 20261h 22mSEV 3
Failures logging in with Vercel CLIVercel reported errors when developers ran vc login with the Vercel CLI, starting around 03:06 UTC on 26 August 2026. The team identified the source and tested a fix, and the incident was resolved at 04:28 UTC. The update text gives no cause and no count of affected users.AI-graded · Dashboard +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Dashboard had a partial outage
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Logging in with the Vercel CLI failed for about 82 minutes, blocking CLI-based deploys and config work; the scope was not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 03:06 UTC · investigating
    We are investigating errors logging in with Vercel CLI (vc login).
  2. 03:15 UTC · investigating
    We are investigating errors logging in with Vercel CLI (vc login).
  3. 04:28 UTC · identified
    The team has identified the source of the issue and is testing a fix.
  4. 04:28 UTC · resolved
    This incident has been resolved.
Source
Aug 25, 202638mSEV 4
Elevated build initialization timesVercel saw elevated initialization times for some builds starting 19:27 UTC on 2026-08-25. It was identified, a fix was implemented, and the incident was resolved at 20:05 UTC. Only build startup was described as slow, and no build failures were reported.AI-graded · some customers · Builds +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds had degraded performance
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Builds took longer to initialize for some deployments for about 40 minutes; the text does not say builds failed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 19:27 UTC · investigating
    We're investigating elevated initialization times for some builds. We will provide updates as we learn more.
  2. 19:37 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 19:57 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 20:05 UTC · resolved
    This incident has been resolved.
Source
Aug 20, 202647mSEV 2
New container functions are failingNewly deployed container functions returned 5XX errors for about 48 minutes; previously working deployments were a workaround.AI-graded · some customers · Functions
Why this grade
  1. RULES · SEV 1
    Sev 1 because Functions had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Newly deployed container functions returned 5XX errors for about 48 minutes; previously working deployments were a workaround.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 17:46 UTC · identified
    We've identified an issue where newly deployed container functions may return 5XX errors. Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.
  2. 18:23 UTC · monitoring
    We have deployed a fix. Newly deployed container functions are working as expected.
  3. 18:34 UTC · resolved
    This incident has been resolved.
Source
Aug 20, 202611mSEV 4
Logs unavailable to query in DashboardRuntime logs could not be queried in the Dashboard for about 11 minutes; log ingestion and build logs were unaffected.AI-graded · Logs +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Logs had a partial outage
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Runtime logs could not be queried in the Dashboard for about 11 minutes; log ingestion and build logs were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 11:14 UTC · investigating
    We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.
  2. 11:21 UTC · monitoring
    We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.
  3. 11:25 UTC · resolved
    The system is operating normally and fully recovered.
Source
Aug 19, 20260mSEV 2
Elevated errors for Workflow streamsSev 2 from the incident title (no components listed)
1 update
  1. 23:00 UTC · resolved
    From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.
Source
Aug 17, 20266h 55mSEV 3
Partial disruption of Observability, Analytics, Firewall, Usage, and Login in DashboardFor about seven hours, Vercel's dashboard had partial disruption to Observability, Web Analytics, Speed Insights, Firewall and Usage. Some customers could not sign in with TOTP codes. Login recovered by 17:51 UTC. Services recovered by 20:13 UTC, but missing observability data was still being ingested at resolution. The provider did not describe the cause in these updates.AI-graded · some customers · Dashboard +8
Why this grade
  1. RULES · SEV 3
    Sev 3 because Dashboard had a partial outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Dashboard login with TOTP failed for some customers, and Firewall, Observability and analytics views were partly disrupted for about seven hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
8 updates
  1. 14:30 UTC · investigating
    We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.
  2. 15:09 UTC · investigating
    We are continuing to investigate this issue. We will share updates as they become available.
  3. 16:06 UTC · investigating
    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. 16:44 UTC · monitoring
    We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available.
  5. 16:46 UTC · monitoring
    We are continuing to monitor for any further issues.
  6. 17:51 UTC · monitoring
    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. 20:13 UTC · monitoring
    Services have recovered. We are still working to ingest missing observability data during this period.
  8. 21:25 UTC · resolved
    Services have recovered. We are still working to ingest missing observability data during this period.
Source
Aug 14, 20260mSEV 3
Dynamic API routes returned 404 errors for some deploymentsSev 3 because Builds had degraded performanceBuilds +1
1 update
  1. 13:08 UTC · resolved
    This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts. Deployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this period were not affected. If your project matches the conditions above and you deployed during the impact window, redeploy your project. Affected deployments are not fixed automatically; a new deployment is required to restore the affected routes.
Source
Aug 6, 20261h 53mSEV 4
Delays delivering log drainsLog drain delivery to customer endpoints was delayed from about 16:37 to 18:29 UTC on August 6, 2026. Delivery recovered and the backlog of delayed logs was processed. The text does not give the number of affected customers or the root cause.AI-graded · Drains +1
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Log drain delivery was delayed for about two hours; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 16:37 UTC · investigating
    We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.
  2. 16:58 UTC · investigating
    We continue to investigate this issue and will provide updates as they become available.
  3. 17:06 UTC · identified
    We've identified the issue and are working on a fix. We will provide updates as they become available.
  4. 17:48 UTC · identified
    We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.
  5. 18:19 UTC · monitoring
    Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.
  6. 18:29 UTC · resolved
    This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.
Source
Jul 25, 202622h 49mSEV 4
Vercel Community temporarily unavailableVercel Community forums were unavailable during a roughly day-long maintenance window; hosting and deploys were not described as affected.AI-graded · Community
Why this grade
  1. RULES · SEV 4
    Sev 4 because Community had degraded performance
  2. CLAUDE · SEV 4 · GLOBAL · MEDIUM CONFIDENCE
    Vercel Community forums were unavailable during a roughly day-long maintenance window; hosting and deploys were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 18:57 UTC · investigating
    The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.
  2. 17:46 UTC · resolved
    Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience.
Source
Jul 23, 20260mSEV 1
Telemetry data loss for DrainsSev 1 because the provider reported data loss or exposure
1 update
  1. 19:00 UTC · resolved
    Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.
Source
Jul 23, 202645mSEV 4
Timeouts loading charts and observability data in DashboardSev 4 because Web Analytics had a partial outageObservability +8
3 updates
  1. 07:33 UTC · investigating
    We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.
  2. 07:55 UTC · monitoring
    The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor.
  3. 08:18 UTC · resolved
    This incident has been resolved.
Source
Jul 23, 202655mSEV 3
Dashboard authentication errorsSev 3 because Dashboard had a major outageDashboard +1
3 updates
  1. 06:47 UTC · investigating
    We are investigating an issue causing the dashboard to be inaccessible for some users.
  2. 07:08 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 07:41 UTC · resolved
    This incident has been resolved.
Source
Jul 17, 20261h 07mSEV 2
Increased invocation failures for Hobby Team functionsSev 2 because Functions had degraded performanceFunctions
4 updates
  1. 14:12 UTC · investigating
    There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.
  2. 14:19 UTC · identified
    We have identified the source of errors and are implementing a fix.
  3. 14:27 UTC · monitoring
    We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.
  4. 15:19 UTC · resolved
    This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.
Source
Jul 16, 20261h 33mSEV 3
GitHub-linked deployments and authentication affectedSev 3 because Builds had degraded performanceDashboard +5
4 updates
  1. 23:09 UTC · investigating
    We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.
  2. 23:39 UTC · identified
    We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.
  3. 00:07 UTC · monitoring
    Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered.
  4. 00:42 UTC · resolved
    This incident has been resolved.
Source
Jul 16, 20262h 06mSEV 1
SAML Single Sign-On (SSO) errorsSev 1 from the incident title (no components listed)SAML Single Sign-On
3 updates
  1. 08:39 UTC · investigating
    We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.
  2. 10:23 UTC · monitoring
    The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor.
  3. 10:45 UTC · resolved
    This incident has been resolved.
Source
Jul 16, 20263h 20mSEV 3
Missing Build CPU Minutes Usage DataSev 3 because Builds had degraded performanceBuilds +1
2 updates
  1. 06:07 UTC · monitoring
    We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
  2. 09:27 UTC · resolved
    The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.
Source
Jul 15, 202630mSEV 3
Errors accessing teams that require 2FASev 3 because API had degraded performanceDashboard +3
3 updates
  1. 23:04 UTC · identified
    We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.
  2. 23:16 UTC · monitoring
    A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available.
  3. 23:34 UTC · resolved
    This incident has been resolved.
Source
Jul 10, 20262h 07mSEV 3
Increased Build failure ratesSev 3 because Builds had degraded performanceBuilds +1
2 updates
  1. 21:22 UTC · monitoring
    We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available. Failed deployments can be retried and should succeed.
  2. 23:28 UTC · resolved
    This incident has been resolved.
Source
Jul 10, 20262h 42mSEV 3
Erroneous budget notificationsSev 3 because Builds had degraded performanceDashboard +3
5 updates
  1. 19:15 UTC · investigating
    We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.
  2. 19:53 UTC · identified
    We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result.
  3. 20:50 UTC · identified
    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. 21:32 UTC · identified
    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. 22:36 UTC · resolved
    We have unpaused all impacted deployments. We will continue to monitor the situation.
Source
Jul 10, 20260mSEV 3
Delays loading Build LogsSev 3 from the incident title (no components listed)
1 update
  1. 13:16 UTC · resolved
    The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.
Source
Jul 8, 20260mSEV 3
Delays Processing BuildsSev 3 because Builds had degraded performanceBuilds +1
5 updates
  1. 18:05 UTC · investigating
    We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.
  2. 18:40 UTC · investigating
    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. 19:13 UTC · monitoring
    Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available.
  4. 19:13 UTC · monitoring
    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. 19:13 UTC · resolved
    This incident has been resolved.
Source
Jul 2, 202615mSEV 2
Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)Sev 2 because CLE1 - Cleveland, East US had degraded performanceDashboard +6
4 updates
  1. 16:31 UTC · investigating
    We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
  2. 16:33 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:39 UTC · monitoring
    A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.
  4. 16:46 UTC · resolved
    This incident has been resolved.
Source
Jul 1, 20261h 33mSEV 2
Increase in Workflow runs stuck in pending, failedSev 2 from the incident title (no components listed)Workflow
3 updates
  1. 16:57 UTC · identified
    We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.
  2. 17:49 UTC · identified
    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. 18:30 UTC · resolved
    The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.
Source
Jun 26, 20262h 06mSEV 3
Intermittent Login Failures on Vercel DashboardSev 3 because Dashboard had a major outageDashboard +1
7 updates
  1. 13:08 UTC · investigating
    We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.
  2. 13:23 UTC · investigating
    We are continuing to investigate this issue.
  3. 14:08 UTC · investigating
    We are continuing to investigate this issue and will provide an update as soon as we have more information.
  4. 14:11 UTC · identified
    The issue has been identified and a fix is being implemented.
  5. 14:29 UTC · identified
    Login is recovering for most users. We're monitoring to ensure stability.
  6. 15:03 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  7. 15:14 UTC · resolved
    This incident has been resolved.
Source
Jun 25, 20265h 58mSEV 1
Increase in Workflow runs stuck as pendingSev 1 from the incident title (no components listed)Workflow
7 updates
  1. 07:45 UTC · investigating
    We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.
  2. 08:27 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 09:25 UTC · identified
    The issue has been identified. We are continuing to work on a fix for this issue.
  4. 10:42 UTC · identified
    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. 12:15 UTC · identified
    We are currently rolling a fix for the issue. We are monitoring the results.
  6. 13:30 UTC · monitoring
    The fix has been fully rolled out and we are monitoring the results.
  7. 13:43 UTC · resolved
    This incident has been resolved.
Source
Jun 23, 202610mSEV 4
Degraded Domain Search in Vercel DashboardSev 4 from the incident title (no components listed)Domain Registration
4 updates
  1. 23:24 UTC · investigating
    We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.
  2. 23:26 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 23:28 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 23:34 UTC · resolved
    This incident has been resolved.
Source
Jun 19, 20260mSEV 1 · SECURITY
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel FunctionsSev 2 because Functions had degraded performance, raised to Sev 1 for securityFunctions
1 update
  1. 17:54 UTC · resolved
    Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.
Source
Jun 16, 20262h 01mSEV 4
Partial disruption of Observability, Analytics, Firewall, and Usage in dashboardSev 4 because Dashboard had degraded performanceDashboard +8
5 updates
  1. 13:39 UTC · investigating
    We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.
  2. 14:45 UTC · investigating
    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. 15:16 UTC · identified
    The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.
  4. 15:26 UTC · monitoring
    The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.
  5. 15:39 UTC · resolved
    The incident has been resolved.
Source
Jun 14, 20264h 21mSEV 1
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)Sev 1 because FRA1 - Frankfurt, Germany, Europe had a partial outageFRA1 - Frankfurt, Germany, Europe +1
6 updates
  1. 21:03 UTC · investigating
    We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
  2. 21:07 UTC · identified
    We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
  3. 21:26 UTC · identified
    The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
  4. 23:15 UTC · identified
    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. 00:25 UTC · monitoring
    All traffic has been restored to the FRA1 Vercel Region.
  6. 01:24 UTC · resolved
    This incident has been resolved.
Source
Jun 9, 202636mSEV 3
Elevated Build Errors for Secure Compute/Static IPs ProjectsSev 3 because Builds had a partial outageBuilds +1
4 updates
  1. 14:09 UTC · investigating
    We are currently investigating this issue.
  2. 14:33 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 14:39 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 14:46 UTC · resolved
    This incident has been resolved.
Source
Jun 8, 20261h 02mSEV 2
Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) RegionSev 2 because Functions had degraded performanceFunctions
5 updates
  1. 18:57 UTC · identified
    The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.
  2. 19:04 UTC · identified
    We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region. If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.
  3. 19:36 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:36 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 20:00 UTC · resolved
    This incident has been resolved.
Source
Jun 1, 202641mSEV 3
Elevated Errors Creating New DeploymentsSev 3 because Builds had degraded performanceBuilds +1
4 updates
  1. 19:21 UTC · investigating
    We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
  2. 19:50 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 19:55 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 20:02 UTC · resolved
    This incident has been resolved.
Source
May 28, 20261h 00mSEV 1
Elevated Function Invocation Errors in Stockholm region (ARN1)Sev 1 because Functions had a partial outageFunctions +4
4 updates
  1. 16:00 UTC · investigating
    We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
  2. 16:18 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:37 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 16:59 UTC · resolved
    This incident has been resolved.
Source
May 27, 202611mSEV 4
Elevated Errors on Vercel Dashboard (Project Overview Page)Sev 4 because Dashboard had degraded performanceDashboard +1
2 updates
  1. 04:50 UTC · investigating
    We are currently investigating this issue.
  2. 05:02 UTC · resolved
    This incident has been resolved. We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.
Source
May 25, 20261h 24mSEV 3
Delays Loading Runtime LogsSev 3 because Logs had degraded performanceLogs
4 updates
  1. 14:58 UTC · investigating
    We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
  2. 15:25 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:05 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 16:22 UTC · resolved
    This incident has been resolved.
Source
May 23, 20260mSEV 3
Elevated Build Failures (GitHub connected projects)Sev 3 because Builds had degraded performanceBuilds +1
7 updates
  1. 10:43 UTC · investigating
    We are currently investigating this issue.
  2. 11:09 UTC · investigating
    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. 12:15 UTC · investigating
    We are continuing to investigate this issue.
  4. 14:30 UTC · investigating
    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. 15:46 UTC · identified
    We have identified the issue and are working closely with GitHub to resolve it.
  6. 18:21 UTC · monitoring
    GitHub has implemented a fix, and we are monitoring the results.
  7. 18:44 UTC · resolved
    This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up25 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.31% up27 incidentsMTTR 55m~$12/mo

README badge

Vercel's live grade, for your README.

Vercel grade badge
[![vercel on downagain.dev](https://downagain.dev/badge/vercel.svg)](https://downagain.dev/p/vercel)