Incident History for Vercel

The incident affecting builds and Git integrations has been resolved.

The backlog of deployment events has been processed and the team continues to monitor build and deployment failures.

Deployment events are delayed and the backlog is being processed while build and deployment failures continue.

Builds and deployments for GitHub-connected projects are still failing while a fix continues.

All services have recovered after delays in Drains, Observability, and Workflow in Washington (iad1).

Delayed Drains deliveries, Observability data, and Build logs have been processed; monitoring continues.

A fix has been implemented and delivery has resumed; delayed Drains deliveries and Observability data are being processed while monitoring continues.

An issue has been identified causing delayed drain delivery, logs, metrics, traces, and pending Workflow runs in Washington (iad1).

Vercel Auth login failures for pages with Deployment Protection enabled have been resolved.

A fix has been implemented for Vercel Auth login failures on pages with Deployment Protection enabled, and results are being monitored.

The issue has been identified and a fix is being implemented for Vercel Auth login failures on pages with Deployment Protection enabled.

Vercel is investigating login failures for pages with Deployment Protection enabled.

The incident involving elevated Sandbox error rates in Paris (cdg1) has been resolved.

A fix has been implemented for elevated Sandbox error rates in Paris (cdg1) and results are being monitored.

Signs of recovery are being seen in Sandbox in Paris (cdg1); updates will follow as available.

Vercel has identified an issue causing elevated Sandbox error rates in Paris (cdg1) and is investigating.

The incident causing build failures and 500 errors for Edge runtime functions has been resolved.

Builds and deployments between 13:01 and 13:11 UTC failed or served 500s; affected customers should re-deploy.

The incident causing elevated errors that triggered deployments in Build & Deploy - Builds has been resolved.

A fix has been implemented for elevated errors triggering deployments in Build & Deploy - Builds, and monitoring is underway.

Vercel has identified the issue causing elevated errors that trigger deployments in Build & Deploy - Builds and is implementing a fix.

Vercel continues investigating elevated errors that trigger deployments in Build & Deploy - Builds.

The incident has been resolved.

The fix has been rolled out and we are seeing signs of recovery for elevated latency in VCR, Blob, and Sandbox API.

Latency recovered for VCR and Sandbox; Blob still under investigation.

The fix for elevated latency in VCR, Blob, and Sandbox API is being rolled out, with another update expected once recovery signs appear.

This incident has been resolved and builds have recovered.

Vercel is continuing to monitor for any further issues with increased deployment failures.

Vercel is seeing recovery in Builds and is continuing to monitor the issue.

Vercel has identified the issue causing increased deployment failures and is working on a fix, with recovery being observed as the fix is deployed.

The incident has been resolved.

The team has identified the source of the issue and is testing a fix.

We are investigating errors logging in with Vercel CLI (vc login).

The incident affecting log querying in the Dashboard has been resolved, and the system is fully operational.

We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.

We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.

Incident resolved. Services have recovered, but we are still working to ingest missing observability data during this period.

Services have recovered, but we are still working to ingest missing observability data during this period.

Login with TOTP has recovered, but we are still working to ingest missing observability data.

A fix has been implemented for the partial disruption affecting Dashboard, Firewall, Observability, Speed Insights, and Web Analytics, and services are recovering.

This incident has been resolved. Between August 12 and 13, some Vercel deployments could return 404 errors from dynamic API routes.

This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.

Log drain delivery has recovered; we are monitoring while remaining delayed deliveries are processed.

We are beginning to see recovery and continue to work on the issue.

We have identified the issue causing delays in log drain delivery and are working on a fix.