Vercel
Vercel AI
No data
Last success —
No component payload
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
7 up0 degraded0 down0 unknown
Snapshot 08:41:05 UTC
updates every 60s
Official incident · Vercel AI
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
resolved · 2026-06-19 17:54:16 UTC · Resolved 2026-06-19 17:54:16 UTC
Duration 1mOfficial title mentions toolnone
Official updates
- 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 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.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
- status.claude.com/api/v2/summary.json
- status.openai.com/api/v2/summary.json + components.json
- status.x.ai/api/compat/summary.json (Cursor)
- status.x.ai/feed.xml (Grok)
- www.githubstatus.com/api/v2/summary.json
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.