Status Checker

Vercel Status

Operational

Last incident: 6/18/2025

Current Status
Overall StatusOperational
Last IncidentIncreased 5xx errors in multiple regions
Incident Statusresolved

Recent Incidents

Increased 5xx errors in multiple regions
6/18/2025, 3:11:40 PM

Jun 18, 15:11 UTC
Resolved - This incident has been resolved.

Jun 18, 14:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 18, 14:08 UTC
Identified - The issue has been identified and a fix is being implemented.

Jun 18, 13:55 UTC
Investigating - We are currently investigating this issue.

Service Disruption: Billing, Team Management, and Plan Upgrades
6/17/2025, 4:58:44 PM

Jun 17, 16:58 UTC
Resolved - This incident has been resolved.

Jun 17, 16:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 17, 15:57 UTC
Investigating - We're currently experiencing issues with an upstream provider affecting usage and invoice viewing, team creation, plan upgrades, product purchases, and access to the v0 plan. We're working to resolve this as quickly as possible.

npm package installs failing with 5xx errors
6/12/2025, 9:19:21 PM

Jun 12, 21:19 UTC
Resolved - This incident has been resolved.

Jun 12, 18:29 UTC
Identified - npm is experiencing degraded performance. Affected users may see 5XX errors when installing packages, which may cause failed builds.

npm status page: https://status.npmjs.org/incidents/dn5mcp85737y

Vercel Dashboard not accessible
6/9/2025, 7:18:39 PM

Jun 9, 19:18 UTC
Resolved - This incident has been resolved.

Jun 9, 18:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 9, 18:43 UTC
Identified - At this time, Vercel Dashboard is inaccessible for all users. We have identified the root cause and are implementing a fix.

Incorrect Edge Functions data shown in Observability
6/6/2025, 10:08:53 PM

Jun 6, 22:08 UTC
Resolved - From 19:27 to 20:40 UTC, the Observability tab showed wrong status codes and error rates for Edge Functions. We’re working on correcting this data, and the correction should be fully completed in the next 12 hours.

Frequently Asked Questions