Vercel Outage History

55 incidents recorded over the last 365 days, 55 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Vercel status99.62% uptime history

Every Recorded Vercel Incident

Vercel incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026New container functions are failingThis incident has been resolved.47 minResolved
Aug 20, 2026Logs unavailable to query in DashboardThe system is operating normally and fully recovered.11 minResolved
Aug 19, 2026Elevated errors for Workflow streamsFrom 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…-88 minResolved
Aug 17, 2026Partial disruption of Observability, Analytics, Firewall, Usage, and Login in DashboardServices have recovered. We are still working to ingest missing observability data during this period.6h 54mResolved
Aug 14, 2026Dynamic API routes returned 404 errors for some deploymentsThis 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…0 minResolved
Aug 6, 2026Delays delivering log drainsThis incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.1h 52mResolved
Jul 25, 2026Vercel Community temporarily unavailableMaintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience.22h 48mResolved
Jul 23, 2026Telemetry data loss for DrainsBetween 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…0 minResolved
Jul 23, 2026Timeouts loading charts and observability data in DashboardThis incident has been resolved.45 minResolved
Jul 23, 2026Dashboard authentication errorsThis incident has been resolved.54 minResolved
Jul 17, 2026Increased invocation failures for Hobby Team functionsThis 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…1h 6mResolved
Jul 16, 2026GitHub-linked deployments and authentication affectedThis incident has been resolved.1h 32mResolved
Jul 16, 2026SAML Single Sign-On (SSO) errorsThis incident has been resolved.2h 5mResolved
Jul 16, 2026Missing Build CPU Minutes Usage DataThe 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.3h 20mResolved
Jul 15, 2026Errors accessing teams that require 2FAThis incident has been resolved.30 minResolved
Jul 10, 2026Increased Build failure ratesThis incident has been resolved.2h 6mResolved
Jul 10, 2026Erroneous budget notificationsWe have unpaused all impacted deployments. We will continue to monitor the situation.2h 42mResolved
Jul 10, 2026Delays loading Build LogsThe 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…-1708 minResolved
Jul 8, 2026Delays Processing BuildsThis incident has been resolved.0 minResolved
Jul 2, 2026Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)This incident has been resolved.14 minResolved
Jul 1, 2026Increase in Workflow runs stuck in pending, failedThe 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…1h 33mResolved
Jun 26, 2026Intermittent Login Failures on Vercel DashboardThis incident has been resolved.2h 5mResolved
Jun 25, 2026Increase in Workflow runs stuck as pendingThis incident has been resolved.5h 58mResolved
Jun 23, 2026Degraded Domain Search in Vercel DashboardThis incident has been resolved.10 minResolved
Jun 19, 2026Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel FunctionsBetween 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…0 minResolved
Jun 16, 2026Partial disruption of Observability, Analytics, Firewall, and Usage in dashboardThe incident has been resolved.2h 0mResolved
Jun 14, 2026Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)This incident has been resolved.4h 20mResolved
Jun 9, 2026Elevated Build Errors for Secure Compute/Static IPs ProjectsThis incident has been resolved.36 minResolved
Jun 8, 2026Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) RegionThis incident has been resolved.1h 2mResolved
Jun 1, 2026Elevated Errors Creating New DeploymentsThis incident has been resolved.40 minResolved
May 28, 2026Elevated Function Invocation Errors in Stockholm region (ARN1)This incident has been resolved.59 minResolved
May 27, 2026Elevated Errors on Vercel Dashboard (Project Overview Page)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.11 minResolved
May 25, 2026Delays Loading Runtime LogsThis incident has been resolved.1h 23mResolved
May 23, 2026Elevated Build Failures (GitHub connected projects)This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt0 minResolved
May 22, 2026Build Failures for Some Next.js DeploymentsBetween 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up…0 minResolved
May 21, 2026Elevated Build ErrorsThis incident has been resolved.6h 29mResolved
May 20, 2026Missing Build CPU Minutes Usage DataThis incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we…10h 0mResolved
May 18, 2026Increased Function Invocation Errors - ERR_MODULE_NOT_FOUNDThis incident has been resolved. Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments…2h 9mResolved
May 18, 2026Support cases cannot be submittedThe incident is resolved and support cases can be submitted again.40 minResolved
May 15, 2026Workflow usage amounts are incorrectly calculatedThe usage tracking system is fully recovered.5h 43mResolved
May 9, 2026Vercel Queues, and Vercel Workflow runs were delayedThis incident has been resolved.54 minResolved
May 8, 2026SSL Certificate Generation DelaysBetween 18:36 and 19:04 UTC, issuing SSL certificates was delayed for new domains. These certificates have now been issued. Certificate renewals were not affected.0 minResolved
May 8, 2026Delays Processing BuildsThis incident has been resolved.10 minResolved
May 8, 2026Elevated errors across multiple services in IAD1 (Washington, D.C., USA)We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in…5h 20mResolved
May 7, 2026Elevated Errors Creating New DeploymentsThis issue has been resolved and new deployments are being created successfully.33 minResolved
May 5, 2026Increased error rate in WorkflowsThis incident has been resolved.49 minResolved
May 5, 2026Failures to load data across multiple services on the Vercel dashboard, API, and CLIAll services remain operational. New data is being processed as expected. The majority of the backfill is complete and a long tail of data will be processed within the next couple of hours.9h 22mResolved
May 4, 2026Request Failures in ICN1 (Seoul, South Korea)Between 21:45–21:52 UTC, some users may have experienced request failures in ICN1. The issue has been identified, a fix has been applied, and the issue has been resolved.-56 minResolved
May 1, 2026Elevated Functions Invocation Errors in ICN1 (Seoul, South Korea) RegionBetween May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content were unaffected…0 minResolved
Apr 30, 2026Elevated Build ErrorsThis incident has been resolved.48 minResolved
Apr 30, 2026Elevated Build Errors for Secure Compute/Static IPs ProjectsThis incident has been resolved.29 minResolved
Apr 29, 2026Elevated Domains ErrorsThis incident has been resolved.1h 14mResolved
Apr 28, 2026Errors Deploying TemplatesThis incident has been resolved.1h 7mResolved
Apr 28, 2026Delayed Usage Data for Observability EventsWe have identified an issue resulting in delayed and/or missing usage data for observability events between 9:00 - 10:30 UTC and 16:50 - 19:30 UTC. The issue has been identified and resolved. Usage data for…0 minResolved
Apr 25, 2026Errors Purchasing Domains, AI Gateway CreditsThis incident has been resolved.3h 39mResolved

How to Read This Vercel Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Vercel acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Vercel outage in this window ran 22h 48m, against a mean recovery of 2h 16m. If you depend on Vercel in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.