Is Vercel Down?
Real-time status check for vercel.com
Checking status...
About Vercel Status
BlueMonitor checks Vercel (vercel.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Degraded Support Case Submission
Mar 31 , 13:29 UTC Resolved - This incident has been resolved. Mar 31 , 13:16 UTC Update - Support case submission has been confirmed to be functioning normally. We will share updates as they become available. Mar 31 , 13:16 UTC Monitoring - A fix has been implemented and we are monitoring the results. We will share updates as they become available. Mar 31 , 13:10 UTC Investigating - We are currently investigating reports of elevated errors when submitting support cases. Some customers may experience timeouts when creating support tickets. We will share updates as they become available.
Elevated Dashboard Errors
Mar 25 , 17:31 UTC Resolved - This incident has been resolved. Mar 25 , 16:41 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 25 , 16:32 UTC Investigating - We are currently investigating reports of elevated error rates on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated Errors Loading Deployments on Dashboard
Mar 24 , 16:31 UTC Resolved - This incident has been resolved. Mar 24 , 16:14 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 24 , 15:19 UTC Investigating - We are currently investigating reports of elevated error rates loading the Deployment Overview on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated errors creating Vercel Functions in sin1 (Singapore)
Mar 24 , 05:01 UTC Resolved - This incident has been resolved. Mar 24 , 04:40 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 24 , 03:43 UTC Identified - We are observing elevated errors creating Vercel Functions in the `sin1` region. To mitigate errors creating deployments, we have temporarily disabled provisioning new Vercel Functions in this region. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated Build Errors
Mar 13 , 23:15 UTC Resolved - This incident has been resolved. Mar 13 , 22:53 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 13 , 22:32 UTC Investigating - We are currently investigating elevated error reports of deployment creation during the build phase. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated GitHub Deployment Failures
Mar 12 , 01:15 UTC Resolved - Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to GitHub API degradations, which they have since resolved. https://www.githubstatus.com/incidents/lw6j95nyw3py https://www.githubstatus.com/incidents/02z04m335tvv
Elevated Latency on Queue Messages, Increased Message Retry Latency in iad1
Mar 6 , 21:22 UTC Resolved - This incident has been resolved. Mar 6 , 21:10 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 6 , 21:00 UTC Identified - The issue has been identified and a fix is being implemented. Mar 6 , 20:53 UTC Investigating - We are investigating reports of elevated queue message latency and message retry latency in iad1, as well as elevated sleep times and increased step retries in Workflow. We will provide additional updates as they become available.
Elevated Errors on Middleware Invocations
Mar 6 , 21:38 UTC Resolved - This incident has been resolved. Mar 6 , 21:20 UTC Monitoring - A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor. Mar 6 , 19:18 UTC Update - We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected. Mar 6 , 15:25 UTC Identified - Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.
Delays Loading Observability, Usage, Analytics, and Speed Insights Data
Mar 3 , 21:10 UTC Resolved - This incident has been resolved. Mar 3 , 19:14 UTC Monitoring - A fix has been implemented and we are seeing recovery for data loading and ingestion across services. We are continuing to monitor and will provide additional updates as they become available. Mar 3 , 17:10 UTC Investigating - Dashboard pages that use Observability data, including Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity, are experiencing delays while loading data. These pages are also experiencing delays ingesting new data. We are investigating this issue and will provide additional updates as they become available.
Dubai region (dxb1) is unavailable and traffic is being re-routed
Mar 16 , 18:44 UTC Resolved - Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available. Mar 2 , 18:23 UTC Monitoring - We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available. Mar 2 , 15:29 UTC Identified - Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatically routed to the nearest region based on the configured settings.
Frequently Asked Questions
Is Vercel down right now?
This page shows the real-time status of Vercel. The status is checked automatically by pinging Vercel's servers. If the status shows "Down", it means Vercel is currently experiencing issues.
Why is Vercel not working?
Vercel may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Vercel is down for everyone?
BlueMonitor checks Vercel's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Vercel is down?
If Vercel is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.