Provider incident title: “Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions”
Started
Friday, June 19, 2026
05:54 PM UTC
Duration
< 1 minute
total
Resolved
05:54 PM UTC
Jun 19, 2026
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.
Get alerted next time
Install Tickerr MCP — your agent auto-reports & routes around outages
When v0 goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.
v0 is back online
View current status and uptime history
v0 30-day uptime: 100% based on Tickerr's independent monitoring checks.
This incident was sourced from v0's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted < 1 minute.
Tickerr monitors 90+ AI tools independently. View live v0 status or all AI tool status.
Get alerted next time v0 goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Also on Tickerr