Provider
VercelIncident detail
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
Resolved incidentMinor1 affected service
Timeline window
to
Outage alerts
Get alerted the next time Vercel breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Vercel posted, oldest to newest, exactly as it appeared on their official status page.
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 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.
Keep exploring
More from Vercel
Neighboring incidents on Vercel's timeline and the rest of their record on OutageDeck.