---
id: "INC-vercel-3h7jsmmrljwt"
kind: "incident"
aliases: []
title: "Vercel: Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions"
severity: "low"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Vercel", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["hosting", "incident", "next.js", "node-fetch", "node.js", "security", "vendor", "vercel"]
not_affected_if: ["not-using-node-fetch-v2", "outside-incident-window"]
published_at: "2026-06-19T17:54:16+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-25T05:31:18+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/clqq0f551l8m", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# Vercel: Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions

A Node.js security release rolled out to Vercel Functions caused intermittent ERR_STREAM_PREMATURE_CLOSE errors for functions using node-fetch@2 between June 19 09:09 and 16:16 UTC. Vercel reverted to the previous Node.js version and says no customer action is required.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Vercel affected ? fixed ?

## How to check

- Look for ERR_STREAM_PREMATURE_CLOSE errors in Vercel Function logs from June 19 09:09 to 16:16 UTC
- Check whether your functions depend on `node-fetch@2` (`npm ls node-fetch`)

## Fix

- No action required according to Vercel; the Node.js upgrade was reverted and functions are operating normally
- Monitor for the upstream fix tracked at https://github.com/nodejs/node/issues/63989 before Vercel re-lands the Node.js upgrade

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/clqq0f551l8m

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_