There were 104 Vercel outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Vercel not working for you?
Vercel not working for you?
Minor
: Vercel deploy builds disrupted by MODULE_NOT_FOUND errors
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(55 minutes)
Vercel experienced a partial outage affecting deployment workflows. Users attempting to create new deployments encountered MODULE_NOT_FOUND errors within the Build & Deploy / Builds component, blocking deployment activity while other platform features remained available. The issue was limited to deployment tasks and did not indicate a full platform failure.
Minor
: Vercel SSL cert delay affects new deployments
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
A brief SSL certificate issuance delay on Vercel prevented access to new deployments over HTTPS for about 10 minutes, while production and preview traffic to existing deployments remained available. The incident began at and was resolved by . The SSL Certificates component was listed as degraded during the event and the provider issued two official updates as the issue was investigated and resolved.
Minor
: Vercel API and dashboard briefly down for 5 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
An outage briefly affected the Vercel Dashboard, the v0 Dashboard, and the Vercel API, causing 5xx errors for a short period. Production and preview deployments were not affected. The outage began at and was resolved by , lasting about 5 minutes. The incident impacted three components: Dashboard, v0 Dashboard, and API.
The provider issued two status updates during the incident, first indicating investigation and later confirming recovery across the affected components.
Minor
: Vercel deployment builds disrupted for ~30 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(30 minutes)
Vercel experienced a partial outage affecting the Build & Deploy / Builds component, preventing new deployment builds from finishing and causing builds to queue. The outage began at and lasted about 30 minutes, impacting developers attempting to deploy applications or release new versions. Builds could be delayed or fail to complete during the incident.
Minor
: Vercel Dashboard: Degraded External API Calls in Observability
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
Vercel's Dashboard component experienced degraded External API Calls data in the Observability tab, with the chart data missing during the incident. End-user traffic remained unaffected. The incident began at and was resolved by , lasting about 1 hour and 10 minutes. The provider issued 2 status updates during the incident, noting an ongoing investigation and later restoration.
Impact was limited to the Observability dashboard data and did not affect services or deployments. The issue was localized to the Dashboard component, and status returned to up at .
Minor
: Vercel brief outage affects team creation and billing access
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
Vercel experienced a brief interruption impacting the Dashboard when creating teams and viewing billing details. Users may have encountered intermittent errors or delays during these actions. The incident began at and was resolved by . The Dashboard component was affected, and the provider posted two official updates during the incident, with services returning to normal afterward.
Minor
: Vercel experiences regional 5xx errors across multiple regions
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(40 minutes)
Vercel reported increased 5xx errors across multiple regions, affecting deployments, previews, and API calls that rely on Vercel's Edge Network, Serverless Functions, and Edge Middleware. The outage began at and lasted about 40 minutes, with services returning to normal by . The incident affected seven components, including Serverless Functions and Edge Network nodes in CPT1 - Cape Town, LHR1 - London, PDX1 - Portland, DUB1 - Dublin, GRU1 - São Paulo, and Edge Middleware.
The provider issued three status updates during the incident. Acknowledging the issue, Vercel said the issue had been identified and a fix was being implemented; a later update confirmed that affected components had returned to normal.
Minor
: Vercel Billing and Team Management Disruption
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(20 minutes)
An outage affected Vercel's Dashboard functionality, disrupting billing, invoice viewing, team creation, plan upgrades, product purchases, and access to the v0 plan. Users may have encountered errors or limited access during the incident. The disruption began at and was resolved by , lasting roughly 20 minutes. The issue was linked to an upstream provider, with the Dashboard component as the primary affected area.
Vercel issued two official updates during the event, confirming the upstream provider issue and ongoing efforts to restore services. The Dashboard returned to normal after the upstream problem was resolved, and status was updated back to the normal state.
Vercel reported degraded npm registry performance, resulting in 5xx errors during npm package installs. This could cause builds to fail for projects deploying on Vercel. The affected component was Build & Deploy / npm Registry, which moved to a degraded state at .
By , the npm Registry returned to normal and the degradation was resolved. The outage lasted approximately 2 hours and 55 minutes.
Minor
: Vercel Dashboard briefly inaccessible for all users
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
Vercel experienced a brief outage affecting the Vercel Dashboard, making the web interface inaccessible for all users. The incident began at and lasted about 10 minutes, with access restored around . The incident was tied to the Dashboard component; the status page stated that the root cause had been identified and a fix was being implemented. The service received two official status updates during the incident, detailing the disruption and subsequent recovery. Once resolved, users could again access the dashboard and manage projects and deployments.