---
id: "INC-vercel-ybx6km0j1gwk"
kind: "incident"
aliases: []
title: "Vercel: Elevated errors for Workflow streams"
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", "ops", "vendor", "vercel"]
not_affected_if: []
published_at: "2026-08-18T23:00:00+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T21:52:55+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/2szns4x5lfs2", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# Vercel: Elevated errors for Workflow streams

## Affected

- vendor:Vercel affected ? fixed ?

## Timeline

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

## From the sources

From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.

---

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