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
Delays delivering log drains
Aug 6 , 18:29 UTC Resolved - This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed. Aug 6 , 18:19 UTC Monitoring - Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed. Aug 6 , 17:48 UTC Update - We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available. Aug 6 , 17:06 UTC Identified - We've identified the issue and are working on a fix. We will provide updates as they become available. Aug 6 , 16:58 UTC Update - We continue to investigate this issue and will provide updates as they become available. Aug 6 , 16:37 UTC Investigating - We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.
Vercel Community temporarily unavailable
Jul 26 , 17:46 UTC Resolved - Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience. Jul 25 , 18:57 UTC Investigating - The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.
Telemetry data loss for Drains
Jul 23 , 19:00 UTC Resolved - Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.
Timeouts loading charts and observability data in Dashboard
Jul 23 , 08:18 UTC Resolved - This incident has been resolved. Jul 23 , 07:55 UTC Monitoring - The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor. Jul 23 , 07:33 UTC Investigating - We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.
Dashboard authentication errors
Jul 23 , 07:41 UTC Resolved - This incident has been resolved. Jul 23 , 07:08 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul 23 , 06:47 UTC Investigating - We are investigating an issue causing the dashboard to be inaccessible for some users.
Increased invocation failures for Hobby Team functions
Jul 17 , 15:19 UTC Resolved - This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected. Jul 17 , 14:27 UTC Monitoring - We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment. Jul 17 , 14:19 UTC Identified - We have identified the source of errors and are implementing a fix. Jul 17 , 14:12 UTC Investigating - There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.
GitHub-linked deployments and authentication affected
Jul 17 , 00:42 UTC Resolved - This incident has been resolved. Jul 17 , 00:07 UTC Monitoring - Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered. Jul 16 , 23:39 UTC Identified - We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available. Jul 16 , 23:09 UTC Investigating - We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.
SAML Single Sign-On (SSO) errors
Jul 16 , 10:45 UTC Resolved - This incident has been resolved. Jul 16 , 10:23 UTC Monitoring - The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor. Jul 16 , 08:39 UTC Investigating - We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.
Missing Build CPU Minutes Usage Data
Jul 16 , 09:27 UTC Resolved - The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard. Jul 16 , 06:07 UTC Monitoring - We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
Errors accessing teams that require 2FA
Jul 15 , 23:34 UTC Resolved - This incident has been resolved. Jul 15 , 23:16 UTC Monitoring - A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available. Jul 15 , 23:04 UTC Identified - We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.
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.