down
Is Vercel down?
Check Vercel availability, incident history, downtime reports, and website performance.
https://vercel.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for Vercel
Last 24 hoursThere is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.
Last collection attempt: 2026-10-20 08:57:03 UTC · Insufficient activity.
No user-submitted outage reports in the last 24 hours.
Vercel outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
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
Current website availability is unknown. No website checks available yet.
Unknown
Successful website checks (24h)
0 successful / 0 measurable checks
Unknown
Median response time
Unknown
95th percentile response time
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-10-22 00:13:12 UTC
67 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Dashboard | operational |
| Builds | operational |
| ARN1 - Stockholm, Sweden | operational |
| Drains | operational |
| Builds | operational |
| Blob | operational |
| Output Generation | operational |
| AI Gateway | operational |
| API | operational |
| BOM1 - Mumbai, India | operational |
| Logs | operational |
| Global Config | operational |
| npm Registry | operational |
| Support Center | operational |
| Dashboard | operational |
| CDG1 - Paris, France, Europe | operational |
| Deploy Hooks | operational |
| Build & Deploy | operational |
| Support Chat | operational |
| Observability | operational |
| CLE1 - Cleveland, East US | operational |
| Git Integrations | operational |
| CI/CD | operational |
| Speed Insights | operational |
| CDN | operational |
| CPT1 - Cape Town, South Africa | operational |
| Web Analytics | operational |
| DUB1 - Dublin, Ireland | operational |
| Community | operational |
| Integration Webhooks | operational |
| Cron Jobs | operational |
| DXB1 - Dubai, UAE | operational |
| FRA1 - Frankfurt, Germany, Europe | operational |
| Dashboard | operational |
| GRU1 - São Paulo, Brazil | operational |
| Data Cache | operational |
| DNS | operational |
| HKG1 - Hong Kong | operational |
| Domain Registration | operational |
| HND1 - Tokyo, Japan | operational |
| IAD1 - Washington DC, USA | operational |
| Firewall | operational |
| ICN1 - Seoul, South Korea | operational |
| Functions | operational |
| Image Optimization | operational |
| KIX1 - Osaka, Japan | operational |
| LHR1 - London, UK | operational |
| Observability | operational |
| PDX1 - Portland, West US | operational |
| SFO1 - San Francisco, CA, USA | operational |
| Marketplace | operational |
| SIN1 - Singapore | operational |
| Queues | operational |
| SYD1 - Sydney, Australia | operational |
| Remote Caching | operational |
| Routing Middleware | operational |
| YUL1 - Montréal, Canada | operational |
| SAML Single Sign-On | operational |
| Sandbox | operational |
| Secure Compute | operational |
| TLS Certificates | operational |
| Storage | operational |
| v0 | operational |
| Workflow | operational |
| Container Registry | operational |
| Key Management Service | operational |
| Connect | operational |
Official incident timeline
Increased build and deployment failures · resolved · 2026-10-12T20:11:12.802Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
- · 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.
- · 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.
- · 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.
- · identified
We have identified the issue and are working on a fix. We will provide additional updates as they become available.
- · 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
- · resolved
All services have recovered.
- · 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.
- · identified
A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.
- · 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
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
The issue has been identified and a fix is being implemented.
- · 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
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.
- · 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
- · resolved
This incident has been resolved.
- · 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.
Deployment stuck in initializing state · resolved · 2026-09-18T22:31:22.780Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · 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.
- · 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.
Elevated Errors Triggering Deployments · resolved · 2026-09-18T21:32:12.937Z
Product match: components.
Read the provider’s incident report
- · resolved
The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
The issue has been identified and a fix is being implemented.
- · investigating
We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.
- · investigating
We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.
Elevated Vercel KMS and Connect Errors · resolved · 2026-09-18T15:14:45.570Z
Product match: unmapped.
Read the provider’s incident report
- · 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.
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: unknown. 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
No recent emerging problem patterns are available for this service.
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.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
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. No public website measurement is available in the current window.
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.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Increased build and deployment failures | 396 min | resolved | |
| Delays in Drains, Observability, and Workflow in Washington (iad1) | 81 min | resolved | |
| Vercel Auth login failures for pages with Deployment Protection enabled | 16 min | resolved | |
| Elevated Sandbox error rates in Paris (cdg1) | 25 min | resolved | |
| Build failures and 500 errors for functions using Edge runtime | 27 min | resolved | |
| Deployment stuck in initializing state | 55 min | resolved | |
| Elevated Errors Triggering Deployments | 50 min | resolved | |
| Missing Web Analytics and Speed Insights data | 1 min | resolved |
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-10-22T00:13:31.000Z.
How many Vercel outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10: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-10-22T00:13:12.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.