Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
Components
Regions
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions Vercel hosts deployments, serverless functions, edge middleware, and the dashboard used to ship frontend and full-stack apps.
resolved · 19 Jun 2026, 17:54 UTC
Between Jun 19 18:09 and Jun 20 01: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.
5
Related incidents
0m
This incident
1h 38m
Avg. resolution time
Faster
vs. average
If your product depends on Vercel, elevated errors during this window often come from upstream, not from your latest commit.
Open official status pageBe the first to know when we launch Pro alerts. No spam — only product updates.
Interested in
This outage lasted 0m. Join the waitlist to get alerted next time.
Join the waitlist for Pro alerts — we'll notify you at launch.