Is Vercel Down?

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.

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.

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.

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.

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.

Jul 10 , 23:28 UTC Resolved - This incident has been resolved. Jul 10 , 21:22 UTC Monitoring - We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available. Failed deployments can be retried and should succeed.

Jul 10 , 22:36 UTC Resolved - We have unpaused all impacted deployments. We will continue to monitor the situation. Jul 10 , 21:32 UTC Update - We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation. We will provide additional updates as they become available. Jul 10 , 20:50 UTC Update - We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner. Jul 10 , 19:53 UTC Identified - We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result. Jul 10 , 19:15 UTC Investigating - We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.

Jul 9 , 13:16 UTC Resolved - The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.

Jul 8 , 19:13 UTC Resolved - This incident has been resolved. Jul 8 , 19:13 UTC Update - The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis. Jul 8 , 19:13 UTC Monitoring - Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available. Jul 8 , 18:40 UTC Update - We are seeing signs of recovery and the affected build queue has started to drain. 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. Jul 8 , 18:05 UTC Investigating - We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.