Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

What to do

• Check whether you use Vercel Functions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-06-19 17:54 UTC and 2026-06-19 17:54 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 1

1. resolvedJun 19, 2026, 5:54 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.