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.
99.988%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
231 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
16m
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 22h

By area

BProduction
8INCIDENTS
11h 13mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 1Oct 6, 2026 · 16mVercel Auth login failures for pages with Deployment Protection enabled
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
Most hit
Sandbox2
Routing Middleware1
Blob1
Storage - Blob1
Worse. 18 in the last 6 months, 0 in the 6 before.
BShipping
14INCIDENTS
23h 23mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Aug 17, 2026 · 6h 55mPartial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard
SEV 3Oct 12, 2026 · 6h 36mIncreased build and deployment failures
SEV 3Aug 26, 2026 · 1h 22mFailures logging in with Vercel CLI
Most hit
Builds7
Build & Deploy - Builds7
Drains2
Logs2
Worse. 27 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 loss1
Sev 2 · BleedingProd degraded or partly down6
Sev 3 · Can't shipCan't deploy, build or manage it12
Sev 4 · PapercutDocs, status page, slow dashboard4

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 17Sev 1–2

Incident history

Show all 50
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 1
Vercel Auth login failures for pages with Deployment Protection enabledSev 1 because Routing Middleware had a partial outageRouting Middleware
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)Sev 2 from the incident title (no components listed)Sandbox
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 stateSev 3 because Builds had degraded performanceBuilds +1
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 3
Elevated Errors Triggering DeploymentsSev 3 because Builds had a partial outageBuilds +1
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 3
Increased deployment failuresSev 3 because Builds had a partial outageBuilds +1
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 CLISev 3 because Dashboard had a partial outageDashboard +1
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 3
Elevated build initialization timesSev 3 because Builds had degraded performanceBuilds +1
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 3
Logs unavailable to query in DashboardSev 3 because Logs had a partial outageLogs +1
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

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B99.98% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C99.99% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.33% up25 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.34% 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)