iszdown
Menu
Service status & outage reports

Is Vercel down?

Check Vercel availability, incident history, downtime reports, and website performance.

https://vercel.com/ ↗
Provider reports operational

Mapped components are operational in the latest status update; individual experiences can vary.

0 recorded outage reports · rolling 24 hours

Estimated activity checked · Text version ↗

My watchlist

Service disruption activity for Vercel

Last 24 hours
0501002026-11-10T04:00:00.000Z: 0.02026-11-10T04:10:00.000Z: 0.02026-11-10T04:20:00.000Z: 0.02026-11-10T04:30:00.000Z: 0.02026-11-10T04:40:00.000Z: 0.02026-11-10T04:50:00.000Z: 0.02026-11-10T05:00:00.000Z: 0.02026-11-10T05:10:00.000Z: 0.02026-11-10T05:20:00.000Z: 0.02026-11-10T05:30:00.000Z: 0.02026-11-10T05:40:00.000Z: 0.02026-11-10T05:50:00.000Z: 0.02026-11-10T06:00:00.000Z: 0.02026-11-10T06:10:00.000Z: 0.02026-11-10T06:20:00.000Z: 0.02026-11-10T06:30:00.000Z: 0.02026-11-10T06:40:00.000Z: 0.02026-11-10T06:50:00.000Z: 0.02026-11-10T07:00:00.000Z: 0.02026-11-10T07:10:00.000Z: 0.02026-11-10T07:20:00.000Z: 0.02026-11-10T07:30:00.000Z: 0.02026-11-10T07:40:00.000Z: 0.02026-11-10T07:50:00.000Z: 0.02026-11-10T08:00:00.000Z: 0.02026-11-10T08:10:00.000Z: 0.02026-11-10T08:20:00.000Z: 0.02026-11-10T08:30:00.000Z: 0.02026-11-10T08:40:00.000Z: 0.02026-11-10T08:50:00.000Z: 0.02026-11-10T09:00:00.000Z: 0.02026-11-10T09:10:00.000Z: 0.02026-11-10T09:20:00.000Z: 0.02026-11-10T09:30:00.000Z: 0.02026-11-10T09:40:00.000Z: 0.02026-11-10T09:50:00.000Z: 0.02026-11-10T10:00:00.000Z: 0.02026-11-10T10:10:00.000Z: 0.02026-11-10T10:20:00.000Z: 0.02026-11-10T10:30:00.000Z: 0.02026-11-10T10:40:00.000Z: 0.02026-11-10T10:50:00.000Z: 0.02026-11-10T11:00:00.000Z: 0.02026-11-10T11:10:00.000Z: 0.02026-11-10T11:20:00.000Z: 0.02026-11-10T11:30:00.000Z: 0.02026-11-10T11:40:00.000Z: 0.02026-11-10T11:50:00.000Z: 0.02026-11-10T12:00:00.000Z: 0.02026-11-10T12:10:00.000Z: 0.02026-11-10T12:20:00.000Z: 0.02026-11-10T12:30:00.000Z: 0.02026-11-10T12:40:00.000Z: 0.02026-11-10T12:50:00.000Z: 0.02026-11-10T13:00:00.000Z: 0.02026-11-10T13:10:00.000Z: 0.02026-11-10T13:20:00.000Z: 0.02026-11-10T13:30:00.000Z: 0.02026-11-10T13:40:00.000Z: 0.02026-11-10T13:50:00.000Z: 0.02026-11-10T14:00:00.000Z: 0.02026-11-10T14:10:00.000Z: 0.02026-11-10T14:20:00.000Z: 0.02026-11-10T14:30:00.000Z: 0.02026-11-10T14:40:00.000Z: 0.02026-11-10T14:50:00.000Z: 0.02026-11-10T15:00:00.000Z: 0.02026-11-10T15:10:00.000Z: 0.02026-11-10T16:00:00.000Z: 0.02026-11-10T16:20:00.000Z: 0.02026-11-10T17:00:00.000Z: 0.02026-11-10T17:20:00.000Z: 0.02026-11-10T18:00:00.000Z: 0.02026-11-10T19:00:00.000Z: 0.02026-11-10T20:00:00.000Z: 0.02026-11-10T20:10:00.000Z: 0.02026-11-10T21:00:00.000Z: 40.02026-11-10T21:10:00.000Z: 0.02026-11-10T21:50:00.000Z: 0.02026-11-10T22:00:00.000Z: 0.02026-11-10T22:20:00.000Z: 0.02026-11-10T23:00:00.000Z: 0.02026-11-10T23:30:00.000Z: 0.02026-11-11T00:00:00.000Z: 0.02026-11-11T00:30:00.000Z: 0.02026-11-11T01:00:00.000Z: 0.02026-11-11T01:40:00.000Z: 0.02026-11-11T02:00:00.000Z: 0.02026-11-11T02:20:00.000Z: 0.02026-11-11T02:50:00.000Z: 0.02026-11-11T03:00:00.000Z: 0.02026-11-11T03:10:00.000Z: 0.02026-11-11T03:20:00.000Z: 0.02026-11-11T03:30:00.000Z: 0.02026-11-11T03:40:00.000Z: 0.024h ago18h ago12h ago6h agoNow
Disruption activity index (0–100). Published incidents and repeated check failures carry more weight than emerging problem patterns. This is not a report count or percentage of affected users. Gaps have no observations; connecting lines do not add measurements.

Observed disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.

Latest observation: 2026-11-11 03:49:27 UTC. Refreshes automatically while this page is visible.

No user-submitted outage reports in the last 24 hours.

Vercel outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

DecJanFebMarAprMayJunJulAugSepOctNov
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Vercel website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-11-11 03:49:27 UTC.

Checked address: https://vercel.com/

DNS lookup: 2 ms · TCP connection: 2 ms · TLS handshake: 6 ms. Certificate expires 2026-12-24; trusted connection: yes.

100%
Successful website checks (24h)
155 successful / 155 measurable checks

91 ms
Median response time

160 ms
95th percentile response time

Successful website response times, 0 to 337 milliseconds337 ms0 ms2026-11-10T03:53:11.000Z: 65 ms2026-11-10T03:58:20.000Z: 59 ms2026-11-10T04:03:29.000Z: 119 ms2026-11-10T04:08:37.000Z: 72 ms2026-11-10T04:13:47.000Z: 92 ms2026-11-10T04:18:54.000Z: 56 ms2026-11-10T04:24:04.000Z: 227 ms2026-11-10T04:29:07.000Z: 103 ms2026-11-10T04:34:10.000Z: 76 ms2026-11-10T04:39:15.000Z: 119 ms2026-11-10T04:44:20.000Z: 95 ms2026-11-10T04:49:25.000Z: 118 ms2026-11-10T04:54:30.000Z: 89 ms2026-11-10T04:59:35.000Z: 106 ms2026-11-10T05:04:40.000Z: 107 ms2026-11-10T05:09:49.000Z: 61 ms2026-11-10T05:14:58.000Z: 71 ms2026-11-10T05:20:09.000Z: 140 ms2026-11-10T05:25:18.000Z: 104 ms2026-11-10T05:30:27.000Z: 55 ms2026-11-10T05:35:36.000Z: 96 ms2026-11-10T05:40:46.000Z: 89 ms2026-11-10T05:45:54.000Z: 99 ms2026-11-10T05:51:03.000Z: 123 ms2026-11-10T05:56:12.000Z: 104 ms2026-11-10T06:01:16.000Z: 116 ms2026-11-10T06:06:21.000Z: 55 ms2026-11-10T06:11:26.000Z: 51 ms2026-11-10T06:16:31.000Z: 126 ms2026-11-10T06:21:36.000Z: 85 ms2026-11-10T06:26:44.000Z: 92 ms2026-11-10T06:31:54.000Z: 92 ms2026-11-10T06:37:04.000Z: 302 ms2026-11-10T06:42:14.000Z: 108 ms2026-11-10T06:47:24.000Z: 69 ms2026-11-10T06:52:32.000Z: 80 ms2026-11-10T06:57:42.000Z: 108 ms2026-11-10T07:02:50.000Z: 91 ms2026-11-10T07:07:58.000Z: 84 ms2026-11-10T07:13:08.000Z: 84 ms2026-11-10T07:18:14.000Z: 48 ms2026-11-10T07:23:19.000Z: 105 ms2026-11-10T07:28:24.000Z: 91 ms2026-11-10T07:33:34.000Z: 199 ms2026-11-10T07:38:42.000Z: 106 ms2026-11-10T07:43:50.000Z: 83 ms2026-11-10T07:49:00.000Z: 120 ms2026-11-10T07:54:10.000Z: 105 ms2026-11-10T07:59:16.000Z: 62 ms2026-11-10T08:04:26.000Z: 156 ms2026-11-10T08:09:36.000Z: 107 ms2026-11-10T08:14:44.000Z: 95 ms2026-11-10T08:19:53.000Z: 89 ms2026-11-10T08:25:03.000Z: 88 ms2026-11-10T08:30:10.000Z: 65 ms2026-11-10T08:35:14.000Z: 229 ms2026-11-10T08:40:19.000Z: 97 ms2026-11-10T08:45:25.000Z: 92 ms2026-11-10T08:50:30.000Z: 132 ms2026-11-10T08:55:34.000Z: 103 ms2026-11-10T09:00:39.000Z: 102 ms2026-11-10T09:05:44.000Z: 103 ms2026-11-10T09:10:49.000Z: 125 ms2026-11-10T09:15:54.000Z: 79 ms2026-11-10T09:20:59.000Z: 74 ms2026-11-10T09:26:05.000Z: 76 ms2026-11-10T09:31:09.000Z: 70 ms2026-11-10T09:36:14.000Z: 55 ms2026-11-10T09:41:22.000Z: 77 ms2026-11-10T09:46:30.000Z: 80 ms2026-11-10T09:51:38.000Z: 93 ms2026-11-10T09:56:48.000Z: 97 ms2026-11-10T10:01:58.000Z: 79 ms2026-11-10T10:07:07.000Z: 86 ms2026-11-10T10:12:14.000Z: 71 ms2026-11-10T10:17:24.000Z: 88 ms2026-11-10T10:22:32.000Z: 86 ms2026-11-10T10:27:42.000Z: 95 ms2026-11-10T10:32:50.000Z: 111 ms2026-11-10T10:37:59.000Z: 130 ms2026-11-10T10:43:05.000Z: 107 ms2026-11-10T10:48:12.000Z: 65 ms2026-11-10T10:53:22.000Z: 97 ms2026-11-10T10:58:32.000Z: 55 ms2026-11-10T11:03:42.000Z: 99 ms2026-11-10T11:08:52.000Z: 84 ms2026-11-10T11:14:04.000Z: 104 ms2026-11-10T11:19:11.000Z: 77 ms2026-11-10T11:24:19.000Z: 56 ms2026-11-10T11:29:28.000Z: 61 ms2026-11-10T11:34:37.000Z: 76 ms2026-11-10T11:39:44.000Z: 85 ms2026-11-10T11:44:50.000Z: 160 ms2026-11-10T11:49:56.000Z: 53 ms2026-11-10T11:55:05.000Z: 54 ms2026-11-10T12:00:14.000Z: 114 ms2026-11-10T12:05:24.000Z: 55 ms2026-11-10T12:10:34.000Z: 97 ms2026-11-10T12:15:43.000Z: 65 ms2026-11-10T12:20:52.000Z: 92 ms2026-11-10T12:26:05.000Z: 66 ms2026-11-10T12:31:11.000Z: 59 ms2026-11-10T12:36:20.000Z: 72 ms2026-11-10T12:41:29.000Z: 90 ms2026-11-10T12:46:38.000Z: 56 ms2026-11-10T12:51:47.000Z: 54 ms2026-11-10T12:56:56.000Z: 337 ms2026-11-10T13:02:06.000Z: 89 ms2026-11-10T13:07:15.000Z: 72 ms2026-11-10T13:12:22.000Z: 63 ms2026-11-10T13:17:32.000Z: 83 ms2026-11-10T13:22:42.000Z: 89 ms2026-11-10T13:27:50.000Z: 69 ms2026-11-10T13:33:00.000Z: 84 ms2026-11-10T13:38:10.000Z: 89 ms2026-11-10T13:43:16.000Z: 88 ms2026-11-10T13:48:27.000Z: 71 ms2026-11-10T13:53:32.000Z: 55 ms2026-11-10T13:58:40.000Z: 91 ms2026-11-10T14:03:48.000Z: 122 ms2026-11-10T14:08:56.000Z: 71 ms2026-11-10T14:14:06.000Z: 55 ms2026-11-10T14:19:17.000Z: 95 ms2026-11-10T14:24:27.000Z: 102 ms2026-11-10T14:29:34.000Z: 68 ms2026-11-10T14:34:44.000Z: 66 ms2026-11-10T14:39:54.000Z: 106 ms2026-11-10T14:45:06.000Z: 156 ms2026-11-10T14:50:14.000Z: 95 ms2026-11-10T14:55:21.000Z: 41 ms2026-11-10T15:00:31.000Z: 162 ms2026-11-10T15:05:40.000Z: 95 ms2026-11-10T15:10:46.000Z: 89 ms2026-11-10T15:15:56.000Z: 108 ms2026-11-10T16:21:48.000Z: 105 ms2026-11-10T17:28:38.000Z: 141 ms2026-11-10T18:00:34.000Z: 152 ms2026-11-10T19:06:27.000Z: 106 ms2026-11-10T20:13:11.000Z: 185 ms2026-11-10T21:19:07.000Z: 91 ms2026-11-10T22:24:48.000Z: 133 ms2026-11-10T23:31:33.000Z: 98 ms2026-11-11T00:38:24.000Z: 120 ms2026-11-11T01:44:08.000Z: 50 ms2026-11-11T02:50:57.000Z: 115 ms2026-11-11T03:03:09.000Z: 159 ms2026-11-11T03:08:14.000Z: 97 ms2026-11-11T03:13:19.000Z: 134 ms2026-11-11T03:18:29.000Z: 118 ms2026-11-11T03:23:39.000Z: 84 ms2026-11-11T03:28:47.000Z: 80 ms2026-11-11T03:33:57.000Z: 87 ms2026-11-11T03:39:07.000Z: 67 ms2026-11-11T03:44:17.000Z: 60 ms2026-11-11T03:49:27.000Z: 58 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Vercel official status · fetched 2026-11-11 03:48:40 UTC

67 mapped components · 0 reporting problems
ComponentProvider status
Dashboardoperational
Buildsoperational
ARN1 - Stockholm, Swedenoperational
Drainsoperational
Buildsoperational
Bloboperational
Output Generationoperational
AI Gatewayoperational
APIoperational
BOM1 - Mumbai, Indiaoperational
Logsoperational
Global Configoperational
npm Registryoperational
Support Centeroperational
Dashboardoperational
CDG1 - Paris, France, Europeoperational
Deploy Hooksoperational
Build & Deployoperational
Support Chatoperational
Observabilityoperational
CLE1 - Cleveland, East USoperational
Git Integrationsoperational
CI/CDoperational
Speed Insightsoperational
CDNoperational
CPT1 - Cape Town, South Africaoperational
Web Analyticsoperational
DUB1 - Dublin, Irelandoperational
Communityoperational
Integration Webhooksoperational
Cron Jobsoperational
DXB1 - Dubai, UAEoperational
FRA1 - Frankfurt, Germany, Europeoperational
Dashboardoperational
GRU1 - São Paulo, Braziloperational
Data Cacheoperational
DNSoperational
HKG1 - Hong Kongoperational
Domain Registrationoperational
HND1 - Tokyo, Japanoperational
IAD1 - Washington DC, USAoperational
Firewalloperational
ICN1 - Seoul, South Koreaoperational
Functionsoperational
Image Optimizationoperational
KIX1 - Osaka, Japanoperational
LHR1 - London, UKoperational
Observabilityoperational
PDX1 - Portland, West USoperational
SFO1 - San Francisco, CA, USAoperational
Marketplaceoperational
SIN1 - Singaporeoperational
Queuesoperational
SYD1 - Sydney, Australiaoperational
Remote Cachingoperational
Routing Middlewareoperational
YUL1 - Montréal, Canadaoperational
SAML Single Sign-Onoperational
Sandboxoperational
Secure Computeoperational
TLS Certificatesoperational
Storageoperational
v0operational
Workflowoperational
Container Registryoperational
Key Management Serviceoperational
Connectoperational

Official incident timeline

Elevated Sandbox and Blob request latency and errors · resolved · 2026-11-10T21:08:33.854Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    On November 10, 2026, between 19:16 and 19:34 UTC, some Sandbox and Blob API requests in iad1 region experienced elevated latency and errors. A fix was applied, restoring service at 19:34 UTC and preventing this issue from recurring. This incident lasted 18 minutes and is being reported retroactively. We apologize for the disruption.

Build delays and degraded Vercel Dashboard performance · resolved · 2026-11-05T18:50:23.139Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved. The build backlog has been cleared.

  2. · monitoring

    We are seeing recovery after taking corrective action to address latency. We are continuing to process delayed builds. Vercel CI has also been affected. We will provide additional updates as they become available.

  3. · investigating

    We've identified an issue where some customers may experience delayed builds, slow page loads, and failed actions in the Vercel Dashboard. We are investigating the cause. We will provide additional updates as they become available.

Delays in Logs and Observability data · resolved · 2026-10-23T17:32:46.920Z

Product match: components.

Read the provider’s incident report

  1. · resolved

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

  2. · identified

    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.

Increased build and deployment failures · resolved · 2026-10-12T20:11:12.802Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

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

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

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

  6. · identified

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

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

Delays in Drains, Observability, and Workflow in Washington (iad1) · resolved · 2026-10-10T01:37:00.920Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    All services have recovered.

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

  3. · identified

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

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

Vercel Auth login failures for pages with Deployment Protection enabled · resolved · 2026-10-06T16:26:49.403Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

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

  3. · identified

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

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

Elevated Sandbox error rates in Paris (cdg1) · resolved · 2026-10-06T09:36:55.249Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

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

  3. · identified

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

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

Build failures and 500 errors for functions using Edge runtime · resolved · 2026-09-28T14:11:29.973Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

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

Recovery tracker

Provider marked the incident resolved; at least three subsequent website checks succeeded.

6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 80 ms · Earlier median: 91 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is vercel down

Query “is vercel” · observed 2026-11-11 03:45:16 UTC · 0 newly observed problem phrases.

Query “vercel” · observed 2026-11-11 03:45:16 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Vercel.

GitHub official status · 2026-11-11 03:50:42 UTC

No active incidents recorded.

Cloudflare official status · 2026-11-11 03:50:42 UTC

About Vercel status on Iszdown

Check Vercel availability, incident history, downtime reports, and website performance.

This page combines the available Vercel report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

67 product-matched official components are listed above. Latest public website measurement: 2026-11-11T03:49:27.000Z.

Visit the official Vercel website · Official provider status · How it works

What to check when Vercel is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Vercel will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Vercel is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Vercel outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

IncidentStarted (UTC)Recorded durationLast collected status
Elevated Sandbox and Blob request latency and errors1 minresolved
Build delays and degraded Vercel Dashboard performance25 minresolved
Delays in Logs and Observability data62 minresolved
Increased build and deployment failures396 minresolved
Delays in Drains, Observability, and Workflow in Washington (iad1)81 minresolved
Vercel Auth login failures for pages with Deployment Protection enabled16 minresolved
Elevated Sandbox error rates in Paris (cdg1)25 minresolved
Build failures and 500 errors for functions using Edge runtime27 minresolved

Frequently asked questions about Vercel

Is Vercel down right now?

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T03:52:30.000Z.

How many Vercel outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T03:50:00.000Z to 2026-11-11T03:50:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Vercel show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Vercel feature.

When was Vercel status last updated?

The latest status observation was 2026-11-11T03:48:40.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Vercel had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Vercel or report a problem?

Use “Watch this service” to save Vercel in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to Vercel

Check a related product separately; its status can differ from Vercel.

Vercel