Delays Processing Builds
This incident has been resolved.
Incident History
Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)
This incident has been resolved.
Increase in Workflow runs stuck in pending, failed
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.
Intermittent Login Failures on Vercel Dashboard
This incident has been resolved.
Increase in Workflow runs stuck as pending
This incident has been resolved.
Degraded Domain Search in Vercel Dashboard
This incident has been resolved.
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
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 caused the errors https://github.com/nodejs/node/issues/63989
We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.
Partial disruption of Observability, Analytics, Firewall, and Usage in dashboard
The incident has been resolved.
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
This incident has been resolved.
Elevated Build Errors for Secure Compute/Static IPs Projects
This incident has been resolved.