Stream reported "Data retrieval issue in US-East" on its status page at 2026-08-05 17:05 UTC.

Stream lists these components: us-east, Chat - us-east.

When did the incident start and end?

It started at 2026-08-05 17:05 UTC and ended at 2026-08-05 21:14 UTC. It lasted 4 h 9 min.

How do I get alerts for Stream?

Subscribe to the Stream live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Stream. outages.live reads it every few minutes and keeps every update.

StreamIncident ·

Data retrieval issue in US-East

ResolvedOfficial update

The incident has been resolved.

The latest update from Stream.

State

Resolved

Started

Lasted

4 h 9 min

Worst impact

Degraded

Timeline

3 updates

17:0518:0719:0920:1221:14

DegradedUpdate postedTimes in UTC

Investigating

4 h 3 min 98%

Identified

6 min 2%

Updates

Times in UTC

As posted by Stream

Resolved

The incident has been resolved.

Identified

The issue has been identified, and our engineering team is working to restore the data to its original state.

Investigating

We are aware of an issue affecting data retrieval for a subset of Chat customers located in the US-East region. Affected customers may see errors or empty results when retrieving messages from channels. Our engineering team is investigating.

Affected components

us-eastChat - us-east

Stream in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 33 min

This incident

1.6× the median

Other Stream incidents

All incidents

Stream·Service disruption in US-East

This incident has been resolved.

Resolved

Follow Stream

Your coding agent knows when Stream is down, and tells you when a failure is theirs, not yours. You can also get Stream incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "stream" and tell me if Stream has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=stream

Slack

/feed subscribe https://outages.live/feed.xml?providers=stream

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane