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
Delayed Firewall Observability Data
Feb 13 , 02:56 UTC Resolved - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC. Feb 13 , 01:52 UTC Update - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC. Feb 12 , 22:59 UTC Monitoring - The issue with delayed firewall observability data has been identified. New data has recovered and old data may be delayed. Feb 12 , 22:41 UTC Investigating - We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Elevated Error Rate on AI Gateway in cle1 and fra1
Feb 11 , 15:00 UTC Resolved - On February 11, 2026, between 15:00 and 19:26 UTC, AI Gateway experienced elevated error rates due to an issue affecting Vercel Functions infrastructure in the cle1 and fra1 Vercel Regions. Requests routed to these regions, including requests originating from other regions, may have experienced failed requests or timeouts during this time. We have resolved the issue, and the service is now operating normally. We apologize for the disruption.
Problems Loading Dashboard & Elevated Builds Error Rate
Feb 7 , 11:18 UTC Resolved - This incident has been resolved. Feb 7 , 10:23 UTC Monitoring - We have applied a fix and are seeing recovery across builds and dashboard. We are continuing to monitor. Feb 7 , 09:35 UTC Identified - We have identified the issue and begun applying a fix. We are beginning to see partial recovery across builds and parts of the dashboard. We will provide additional updates as they become available. Feb 7 , 08:38 UTC Investigating - We are investigating elevated dashboard load times and error rates on builds. We will provide updates as they become available.
Delays Loading Firewall, Billing, and Observability Data
Feb 5 , 20:51 UTC Resolved - This incident has been resolved. Feb 5 , 19:35 UTC Monitoring - A fix has been implemented and we are beginning to see gradual recovery. We are actively monitoring results and will share more updates as they become available. Feb 5 , 18:28 UTC Update - We are continuing to implement a fix for delays in data appearing in the dashboard for firewall, billing, and observability. We will share additional updates as they become available. Feb 5 , 16:53 UTC Identified - The issue has been identified and a fix is being implemented. Feb 5 , 16:11 UTC Investigating - We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Elevated Error Rates on Sandboxes
Feb 3 , 21:54 UTC Resolved - This issue has been resolved and sandboxes are creating normally. Feb 3 , 20:14 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 3 , 19:51 UTC Update - We are releasing a fix and are continuing to work on stabilizing sandbox creation. Feb 3 , 18:49 UTC Update - We are continuing to work on a fix for this issue. Feb 3 , 18:38 UTC Identified - We have identified an issue while creating new sandboxes. We are working on a fix for the issue.
Elevated latency creating new deployments
Feb 3 , 21:36 UTC Resolved - The issue has been resolved and all deployments are building normally. Feb 3 , 21:12 UTC Monitoring - A fix has been applied resolving the queue for new deployments. We are continuing to monitor the results. Feb 3 , 20:48 UTC Investigating - We are investigating elevated latency creating new deployments. Some deployments may be delayed.
Elevated Errors on API & Dashboard, Delayed Builds
Feb 3 , 17:30 UTC Resolved - This incident has been resolved. Feb 3 , 16:50 UTC Monitoring - A fix has been implemented, and we are monitoring results. Feb 3 , 16:22 UTC Update - We have begun applying fixes and are seeing partial recovery across API, dashboard, and builds. We are continuing to apply fixes. We will share additional updates as they become available. Feb 3 , 15:43 UTC Identified - The issue has been identified, and we are working on a fix. Feb 3 , 15:43 UTC Update - We are continuing to investigate this issue. Feb 3 , 15:22 UTC Investigating - We are currently investigating reports of elevated error rates and slowness on the Vercel Dashboard and APIs. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Elevated error rates in sin1 (Singapore) Edge Region
Feb 1 , 08:57 UTC Resolved - There were elevated error rates in the sin1 (Singapore) edge region between 08:57 and 09:04 UTC. The issue has been resolved, and all systems are operating normally.
Elevated git clone duration at build time
Jan 30 , 11:08 UTC Resolved - This incident has been resolved. Jan 30 , 10:42 UTC Monitoring - The new build routing has addressed the issue. We are monitoring the results. Jan 30 , 10:24 UTC Update - We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause. Jan 30 , 09:02 UTC Update - We are continuing to investigate this issue. Jan 30 , 06:21 UTC Update - We are continuing to investigate this issue. Jan 30 , 03:34 UTC Update - We’ve confirmed the issue is intermittent, and redeploying a failed build may succeed. Alternatively, as a temporary workaround, builds can be run locally and deployed as prebuilt output using Vercel CLI: `vercel build && vercel deploy --prebuilt` Jan 29 , 16:00 UTC Investigating - We are currently observing elevated `git clone` durations on a subset of builds. Some builds are taking significantly longer than expected to clone repositories, resulting in slower overall build start times. We are actively analyzing clone performance metrics and infrastructure behavior to identify the root cause.
Elevated Connection Latency in dub1 (Dublin, Ireland) Edge Region
Jan 28 , 20:21 UTC Resolved - This incident has been resolved, and traffic has been fully routed back to the dub1 region. Jan 28 , 19:56 UTC Monitoring - A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results. Jan 28 , 18:27 UTC Update - We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1. Jan 28 , 17:43 UTC Update - The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue. Jan 28 , 17:19 UTC Identified - We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
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.