Changes / Vercel / Elevated Errors Triggering Deployments
Vercel: Major incident: Elevated Errors Triggering Deployments
Summary
Vercel reported a major incident causing elevated errors triggering deployments in Build & Deploy - Builds, Builds, starting at 2026-09-18 20:32 UTC and resolved at 2026-09-18 21:22 UTC; the computed duration was 49 min. A fix was implemented; existing deployments and traffic were unaffected, and no customer action was required.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Elevated Errors Triggering Deployments
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-18 20:32 UTC
Before: not present
After: 2026-09-18 21:22 UTC
Before: not present
After: Build & Deploy - Builds, Builds
Before: not present
After: We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.
Before: not present
After: We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.
Before: not present
After: The issue has been identified and a fix is being implemented.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: The issue causing elevated errors triggering deployments has been resolved.
Existing deployments and traffic are unaffected and no action is required.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Elevated Errors Triggering Deployments (this change) Vercel reported a major incident causing elevated errors triggering deployments in Build & Deploy - Builds, Builds, starting at 2026-09-18 20:32 UTC and resolved at 2026-09-18 21:22 UTC; the computed duration was 49 min. A fix was implemented; existing deployments and traffic were unaffected, and no customer action was required. | Major incident |