Vercel incident

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

Notice Resolved View vendor source →

Vercel experienced a notice incident on June 19, 2026 affecting Functions, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 19, 2026, 05:54 PM UTC
Resolved
Jun 19, 2026, 05:54 PM UTC
Duration
—
Detected by Pingoru
Jun 19, 2026, 05:54 PM UTC

Affected components

Functions

Update timeline

  1. resolved Jun 19, 2026, 05:54 PM UTC

    Between Jun 19 09:09 and Jun 20 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.