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.
Jul 23, 19:00 UTC Resolved - Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Log Drains was not delivered. Logs, traces, and events emitted via drains during this window were dropped and are unrecoverable.Customers with one or more Log Drains configured on their Vercel projects lost telemetry emitted during the affected window. Data emitted outside the 19:12 and 19:18 UTC…
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 -…
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.
Jul 17, 15:19 UTC Resolved - This incident has been resolved. 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 an…
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…
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…
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 a…
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…
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 we…
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 a…
Jul 2, 16:46 UTC Resolved - This incident has been resolved. Jul 2, 16:39 UTC Monitoring - A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor. Jul 2, 16:33 UTC Identified - The issue has been identified and a fix is being implemented. Jul 2, 16:31 UTC Investigating - We are investigating an…
Jul 1, 18:30 UTC Resolved - The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected.Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state. Jul 1, 17:49 UTC Update - We ar…
Jun 26, 15:14 UTC Resolved - This incident has been resolved. Jun 26, 15:03 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 26, 14:29 UTC Update - Login is recovering for most users. We're monitoring to ensure stability. Jun 26, 14:11 UTC Identified - The issue has been identified and a fix is being implemented. Jun 26, 14:08 UTC Update - We are continuing to inv…
Jun 25, 13:43 UTC Resolved - This incident has been resolved. Jun 25, 13:30 UTC Monitoring - The fix has been fully rolled out and we are monitoring the results. Jun 25, 12:15 UTC Update - We are currently rolling a fix for the issue. We are monitoring the results. Jun 25, 10:42 UTC Update - We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow r…
Jun 23, 23:34 UTC Resolved - This incident has been resolved. Jun 23, 23:28 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 23, 23:26 UTC Identified - The issue has been identified and a fix is being implemented. Jun 23, 23:24 UTC Investigating - We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.
Jun 19, 17:54 UTC Resolved - Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE.As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which…
Jun 16, 15:39 UTC Resolved - The incident has been resolved. Jun 16, 15:26 UTC Monitoring - The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor. Jun 16, 15:16 UTC Identified - The team has identified the source of the issue and is preparing a fix for timeouts and failed…
Jun 15, 01:24 UTC Resolved - This incident has been resolved. Jun 15, 00:25 UTC Monitoring - All traffic has been restored to the FRA1 Vercel Region. Jun 14, 23:15 UTC Update - The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished. Jun 14, 21:26 UTC Update - The impact…
Jun 9, 14:46 UTC Resolved - This incident has been resolved. Jun 9, 14:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 9, 14:33 UTC Identified - The issue has been identified and a fix is being implemented. Jun 9, 14:09 UTC Investigating - We are currently investigating this issue.
Jun 8, 20:00 UTC Resolved - This incident has been resolved. Jun 8, 19:36 UTC Update - We are continuing to monitor for any further issues. Jun 8, 19:36 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 8, 19:04 UTC Update - We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the n…
Jun 1, 20:02 UTC Resolved - This incident has been resolved. Jun 1, 19:55 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 1, 19:50 UTC Identified - The issue has been identified and a fix is being implemented. Jun 1, 19:21 UTC Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide addi…
May 28, 16:59 UTC Resolved - This incident has been resolved. May 28, 16:37 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 28, 16:18 UTC Identified - The issue has been identified and a fix is being implemented. May 28, 16:00 UTC Investigating - We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1…
May 27, 05:02 UTC Resolved - This incident has been resolved.We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC. May 27, 04:50 UTC Investigating - We are currently investigating this issue.
May 25, 16:22 UTC Resolved - This incident has been resolved. May 25, 16:05 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 25, 15:25 UTC Identified - The issue has been identified and a fix is being implemented. May 25, 14:58 UTC Investigating - We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains ar…
May 23, 18:44 UTC Resolved - This incident has been resolved.Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt May 23, 18:21 UTC Monitoring - GitHub has implemented a fix, and we are monitoring the results. May 23, 15:46 UTC Identified - We have identified the issue and are working closely with GitHub to resolve it. May 23, 14:30 UTC Up…
May 22, 17:11 UTC Resolved - Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
May 21, 21:31 UTC Resolved - This incident has been resolved. May 21, 21:20 UTC Monitoring - The mitigation was successfully rolled out, and builds are stable. May 21, 19:55 UTC Update - The root cause has been identified and we are rolling out a mitigation. May 21, 15:01 UTC Identified - We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deploymen…