Vercel outage history

An outage affected Vercel's container functions, with newly deployed container functions returning 5XX errors. The incident began at Aug 20, 2026 5:51 PM UTC and impacted the ability to deploy or run fresh container logic. As a temporary workaround, teams could reuse a previously working container function deployment while Vercel investigated. This issue limited to the new container function deployments and did not indicate a broader platform failure.

Users could not query runtime logs in the Vercel Dashboard during a brief outage. The issue began at 11:16 AM UTC and was resolved by 11:26 AM UTC. The problem affected only runtime log queries in the Dashboard; log ingestion and logging for builds remained available. The Observability / Logs component briefly degraded (listed as warn) and then returned to normal, with impact limited to the dashboard logging experience and no impact to other logging services.

Vercel’s Dashboard experienced a partial disruption that affected Observability, Analytics, Firewall, and Usage features, with users reporting dashboards not loading or responding. The incident began around 2:31 PM UTC as the status page noted a partial disruption across key dashboard components. A user in Gothenburg reported not responding at 5:13 PM UTC, illustrating the user experience during the event.

Vercel experienced delays delivering log drains, affecting the Observability / Drains component and the timely delivery of logs used for monitoring and debugging. The issue began around 4:41 PM UTC when the status page reported delays in log drain delivery, and engineers worked to identify the cause and implement a fix.

By 5:06 PM UTC, the team had identified the issue and were actively working on a resolution. Signs of recovery appeared by 5:51 PM UTC, and by 6:21 PM UTC log drain delivery had recovered while remaining delayed deliveries were being processed. The component returned to full operation at 6:31 PM UTC.

Users attempting to access the Vercel Community forums encountered an outage while the Community component underwent maintenance. The interruption began at 7:01 PM UTC and prevented posting or reading discussions.

Access was restored when the maintenance completed at 5:51 PM UTC, roughly 22 hours after the issue began. The status page indicated the Community was under maintenance during this period, with services returning to normal as the component transitioned back to an active state.

Users of the Vercel Dashboard encountered timeouts when loading charts and observability data, affecting dashboards for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. The issue began at 7:36 AM UTC and caused chart rendering to fail. The Dashboard briefly recovered by 7:46 AM UTC, but a renewed issue surfaced around 7:56 AM UTC before full restoration.

Vercel's status updates indicated the team identified the source of the problem and implemented a fix, and charts and observability data started loading again, with all components returning to normal by 8:21 AM UTC. The incident represented a partial outage affecting dashboard visibility rather than a broader platform failure.

An outage hit Vercel's Dashboard, starting with authentication errors that left the Dashboard inaccessible for some users. The disruption began at 6:51 AM UTC and a fix was deployed by 7:11 AM UTC, but impact persisted as users encountered timeouts when loading charts and observability data. This affected multiple dashboard areas and components.

Between 2:16 PM UTC and 3:21 PM UTC, Vercel reported increased invocation failures for Hobby Team functions in new deployments, while existing deployments continued to operate normally. The issue affected new deployments, causing invocation errors for users deploying fresh code. A fix was deployed and monitoring continued; by 3:21 PM UTC the Functions component had returned to normal, and rolling back to a previous deployment or redeploying were recommended workarounds.

The issue began at Jul 16, 2026 11:11 PM UTC with elevated error rates for signing in to Vercel using GitHub. Sign-in via email remained unaffected, but GitHub authentication and GitHub-linked deployments were impacted, causing degraded workflow for projects tied to GitHub repositories. The problem broadened at Jul 16, 2026 11:41 PM UTC to affect GitHub login, signup, and account connections as well as deployments, with related components in CI/CD / Git Integrations and Build & Deploy / Builds showing degraded status. Users attempting to start or trigger builds could experience delays or initializes issues during the impact window.

Users attempting to sign in with SAML Single Sign-On could not log in or access SSO-protected teams in the Vercel dashboard and via the CLI. The issue began at 8:46 AM UTC and affected the SAML Single Sign-On component, which remained degraded through the incident. Build & Deploy / Builds experienced a brief degradation and recovered by 9:31 AM UTC, while SAML SSO continued to be affected until full recovery. The incident resolved after about 1 hour 40 minutes, with SAML SSO returning to normal later in the morning.