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
Workflow usage amounts are incorrectly calculated
May 15 , 16:18 UTC Resolved - The usage tracking system is fully recovered. May 15 , 15:39 UTC Monitoring - The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor. May 15 , 13:40 UTC Update - We are continuing to work on the fix. Usage tracking for Workflow Storage remains paused. The incorrect calculations will not be charged. May 15 , 11:37 UTC Identified - The team has identified the source of the incorrect usage data calculations and has paused usage tracking while a fix is being prepared. May 15 , 10:34 UTC Investigating - Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.
Vercel Queues, and Vercel Workflow runs were delayed
May 9 , 05:40 UTC Resolved - This incident has been resolved. May 9 , 04:45 UTC Monitoring - Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.
SSL Certificate Generation Delays
May 8 , 19:15 UTC Resolved - Between 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.
Delays Processing Builds
May 8 , 16:41 UTC Resolved - This incident has been resolved. May 8 , 16:33 UTC Monitoring - We have applied a fix and are observing recovery across all builds. We'll provide additional updates as-needed. May 8 , 16:30 UTC Identified - We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they become available.
Elevated errors across multiple services in IAD1 (Washington, D.C., USA)
May 8 , 06:39 UTC Resolved - 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 the IAD1 region. May 8 , 04:54 UTC Monitoring - We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours. May 8 , 02:33 UTC Update - New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated. May 8 , 02:18 UTC Update - We are continuing to work on a fix for this issue. May 8 , 02:13 UTC Update - New messages to Vercel Workflows and Vercel Queues are being queued, but message processing is paused. Queued messages will be processed when service is restored. May 8 , 01:47 UTC Update - Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1. May 8 , 01:18 UTC Identified - Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.
Elevated Errors Creating New Deployments
May 7 , 21:48 UTC Resolved - This issue has been resolved and new deployments are being created successfully. May 7 , 21:14 UTC Investigating - We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes available.
Increased error rate in Workflows
May 6 , 00:19 UTC Resolved - This incident has been resolved. May 6 , 00:13 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 5 , 23:30 UTC Identified - We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue and are implementing a fix.
Failures to load data across multiple services on the Vercel dashboard, API, and CLI
May 6 , 00:38 UTC Resolved - All 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. May 5 , 17:14 UTC Update - All systems are operational. We are continuing to monitor the backfill process, which is expected to take a couple of hours. New data is being processed as expected. May 5 , 17:12 UTC Update - We are continuing to monitor for any further issues. May 5 , 16:50 UTC Monitoring - Impacted services have recovered. We are continuing to monitoring, while backfilling remaining missing data. May 5 , 16:37 UTC Update - Reading data from impacted services has recovered. We are working to backfill any missing data in Observability. May 5 , 16:30 UTC Update - We are seeing services start to recover as we incrementally apply the fix. May 5 , 15:58 UTC Update - We are continuing to work on a fix for this issue. May 5 , 15:15 UTC Identified - We've identified an issue where various services in the Vercel dashboard, API, and CLI are failing to load data. These services include Observability, Speed Insights, Alerts, Usage, Web Analytics, Firewall, and CDN observability. Broadly, areas backed by analytical data are affected. We have identified the issue and are working on a fix. Production applications running on Vercel are not impacted.
Request Failures in ICN1 (Seoul, South Korea)
May 4 , 21:30 UTC Resolved - 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.
Elevated Functions Invocation Errors in ICN1 (Seoul, South Korea) Region
May 1 , 11:30 UTC Resolved - Between 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 this time. We have reverted the change that caused the issue to mitigate this.
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.