# Vercel outage reports and status Canonical page: https://iszdown.com/now/vercel Status: Provider reports operational 24-hour window (UTC): 2026-10-21T01:00:00.000Z to 2026-10-22T01:00:00.000Z Recorded outage reports in this window: 0 Last successful estimated-activity check: No usable observation available Check Vercel availability, incident history, downtime reports, and website performance. ## How to interpret this page Estimated down reports are based on US problem-related activity. Values are relative activity from 0 to 100, not counts of submitted reports. The HTML chart averages samples into ten-minute intervals. Partial samples are excluded and missing samples are not invented. Recorded outage reports and estimated activity are separate signals. Neither confirms that every user is affected. Missing or stale data does not establish that a service is working. Methodology: https://iszdown.com/methodology ## Citation Cite [Vercel on Iszdown](https://iszdown.com/now/vercel), include your access time and the observation time above, and qualify estimated activity as an estimate. Recheck before describing current status. Iszdown is independent of the monitored provider. ## Estimated activity samples No usable activity samples are available for this service in this window. ## Evidence and recovery Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. No recent recovery can be established from available evidence. ## Website measurements Successful sampled checks (24h): Unknown (0/0). Restricted checks: 0. Median response: Unknown ms. P95 response: Unknown ms. These are sampled public website checks from one US server, not continuous uptime or authenticated app/API tests. Missing data stays unknown. ## Official provider evidence Updated 2026-10-22T00:59:49.000Z. - 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 - [Increased build and deployment failures](https://stspg.io/cfrfjg8fqxfr): resolved; updated 2026-10-12T20:11:12.802Z - [Delays in Drains, Observability, and Workflow in Washington (iad1)](https://stspg.io/mz4bqspyxvy7): resolved; updated 2026-10-10T01:37:00.920Z - [Vercel Auth login failures for pages with Deployment Protection enabled](https://stspg.io/l76txmwrzdcp): resolved; updated 2026-10-06T16:26:49.403Z - [Elevated Sandbox error rates in Paris (cdg1)](https://stspg.io/sgzd0v141vpk): resolved; updated 2026-10-06T09:36:55.249Z - [Build failures and 500 errors for functions using Edge runtime](https://stspg.io/p633qkgvpdsy): resolved; updated 2026-09-28T14:11:29.973Z - [Deployment stuck in initializing state](https://stspg.io/fx0fjwcpvdqr): resolved; updated 2026-09-18T22:31:22.780Z - [Elevated Errors Triggering Deployments](https://stspg.io/6c79t86c2xrr): resolved; updated 2026-09-18T21:32:12.937Z - [Elevated Vercel KMS and Connect Errors](https://stspg.io/fzs89dpp3ghz): resolved; updated 2026-09-18T15:14:45.570Z ## Daily outage history Dates use America/New_York. Green means no issues observed with sufficient monitoring; pink means official incidents, repeated website failures, or reports from at least three network addresses. Gray means insufficient coverage. These are daily evidence summaries, not guaranteed uptime. | Date | Daily assessment | Observed hours | Official incidents | | --- | --- | --- | --- | | 2025-11-04 | Service issues detected | 0 | 1 | | 2025-11-11 | Service issues detected | 0 | 1 | | 2025-11-14 | Service issues detected | 0 | 1 | | 2025-11-16 | Service issues detected | 0 | 1 | | 2025-11-17 | Service issues detected | 0 | 1 | | 2025-11-18 | Service issues detected | 0 | 1 | | 2025-11-26 | Service issues detected | 0 | 1 | | 2025-12-02 | Service issues detected | 0 | 1 | | 2025-12-07 | Service issues detected | 0 | 1 | | 2025-12-08 | Service issues detected | 0 | 1 | | 2025-12-09 | Service issues detected | 0 | 1 | | 2025-12-10 | Service issues detected | 0 | 1 | | 2025-12-12 | Service issues detected | 0 | 2 | | 2026-01-13 | Service issues detected | 0 | 1 | | 2026-01-14 | Service issues detected | 0 | 1 | | 2026-01-22 | Service issues detected | 0 | 1 | | 2026-01-26 | Service issues detected | 0 | 1 | | 2026-01-28 | Service issues detected | 0 | 1 | | 2026-01-29 | Service issues detected | 0 | 1 | | 2026-01-30 | Service issues detected | 0 | 1 | | 2026-02-03 | Service issues detected | 0 | 3 | | 2026-02-05 | Service issues detected | 0 | 1 | | 2026-02-07 | Service issues detected | 0 | 1 | | 2026-02-12 | Service issues detected | 0 | 1 | | 2026-03-01 | Service issues detected | 0 | 1 | | 2026-03-02 | Service issues detected | 0 | 3 | | 2026-03-03 | Service issues detected | 0 | 2 | | 2026-03-04 | Service issues detected | 0 | 1 | | 2026-03-05 | Service issues detected | 0 | 1 | | 2026-03-06 | Service issues detected | 0 | 3 | | 2026-03-07 | Service issues detected | 0 | 1 | | 2026-03-08 | Service issues detected | 0 | 1 | | 2026-03-09 | Service issues detected | 0 | 1 | | 2026-03-10 | Service issues detected | 0 | 1 | | 2026-03-11 | Service issues detected | 0 | 1 | | 2026-03-12 | Service issues detected | 0 | 1 | | 2026-03-13 | Service issues detected | 0 | 2 | | 2026-03-14 | Service issues detected | 0 | 1 | | 2026-03-15 | Service issues detected | 0 | 1 | | 2026-03-16 | Service issues detected | 0 | 1 | | 2026-03-23 | Service issues detected | 0 | 1 | | 2026-03-24 | Service issues detected | 0 | 2 | | 2026-03-25 | Service issues detected | 0 | 1 | | 2026-03-31 | Service issues detected | 0 | 2 | | 2026-04-01 | Service issues detected | 0 | 1 | | 2026-04-02 | Service issues detected | 0 | 2 | | 2026-04-07 | Service issues detected | 0 | 2 | | 2026-04-19 | Service issues detected | 0 | 1 | | 2026-04-20 | Service issues detected | 0 | 3 | | 2026-04-21 | Service issues detected | 0 | 1 | | 2026-04-22 | Service issues detected | 0 | 2 | | 2026-04-24 | Service issues detected | 0 | 1 | | 2026-04-25 | Service issues detected | 0 | 1 | | 2026-04-28 | Service issues detected | 0 | 2 | | 2026-04-29 | Service issues detected | 0 | 1 | | 2026-04-30 | Service issues detected | 0 | 2 | | 2026-05-04 | Service issues detected | 0 | 1 | | 2026-05-05 | Service issues detected | 0 | 2 | | 2026-05-07 | Service issues detected | 0 | 2 | | 2026-05-08 | Service issues detected | 0 | 2 | | 2026-05-09 | Service issues detected | 0 | 1 | | 2026-05-15 | Service issues detected | 0 | 1 | | 2026-05-18 | Service issues detected | 0 | 2 | | 2026-05-20 | Service issues detected | 0 | 1 | | 2026-05-21 | Service issues detected | 0 | 2 | | 2026-05-23 | Service issues detected | 0 | 1 | | 2026-05-25 | Service issues detected | 0 | 1 | | 2026-05-27 | Service issues detected | 0 | 1 | | 2026-05-28 | Service issues detected | 0 | 1 | | 2026-06-01 | Service issues detected | 0 | 1 | | 2026-06-08 | Service issues detected | 0 | 1 | | 2026-06-09 | Service issues detected | 0 | 1 | | 2026-06-14 | Service issues detected | 0 | 1 | | 2026-06-16 | Service issues detected | 0 | 1 | | 2026-06-23 | Service issues detected | 0 | 1 | | 2026-06-25 | Service issues detected | 0 | 1 | | 2026-06-26 | Service issues detected | 0 | 1 | | 2026-07-01 | Service issues detected | 0 | 1 | | 2026-07-02 | Service issues detected | 0 | 1 | | 2026-07-08 | Service issues detected | 0 | 1 | | 2026-07-10 | Service issues detected | 0 | 2 | | 2026-07-15 | Service issues detected | 0 | 1 | | 2026-07-16 | Service issues detected | 0 | 3 | | 2026-07-17 | Service issues detected | 0 | 1 | | 2026-07-23 | Service issues detected | 0 | 3 | | 2026-08-06 | Service issues detected | 0 | 1 | | 2026-08-17 | Service issues detected | 0 | 1 | | 2026-08-20 | Service issues detected | 0 | 2 | | 2026-08-25 | Service issues detected | 0 | 2 | | 2026-08-26 | Service issues detected | 0 | 1 | | 2026-09-01 | Service issues detected | 0 | 1 | | 2026-09-04 | Service issues detected | 0 | 1 | | 2026-09-10 | Service issues detected | 0 | 1 | | 2026-09-16 | Service issues detected | 0 | 1 | | 2026-09-18 | Service issues detected | 0 | 2 | | 2026-09-28 | Service issues detected | 0 | 1 | | 2026-10-06 | Service issues detected | 0 | 2 | | 2026-10-09 | Service issues detected | 0 | 1 | | 2026-10-12 | Service issues detected | 0 | 1 | | 2026-10-20 | No issues observed | 24 | 0 | | 2026-10-21 | Good so far | 21 | 0 | ## About Vercel monitoring 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. ## Troubleshooting ### 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. ## Frequently asked questions ### 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-22T01:01:44.000Z. ### How many Vercel outage reports are there today? The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T01:00:00.000Z to 2026-10-22T01:00: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:59:49.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 - [Vercel](https://iszdown.com/now/vercel)