rewindex

CompaniesVercelIncidents

Vercel: Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestspg.io (opens in new tab)

Affected components: Functions

Timeline of updates

  1. 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 (opens in new tab)

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Vercel, started 2026-06-19 17:54 UTC, resolved after 0 min, 1 update(s).

Title
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
Vendor
Vercel
Date
URL
https://rewindex.com/company/vercel/incidents/3h7jsmmrljwt

Vercel profileRecent Vercel incidentsAll outages on June 19, 2026Vercel in June 2026MarkdownJSON