Data retrieval issue in US-East
The incident has been resolved.
The latest update from Stream.
State
Resolved
Started
Lasted
4 h 9 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
4 h 3 min 98%
Identified
6 min 2%
Updates
Times in UTCAs posted by Stream
The incident has been resolved.
The issue has been identified, and our engineering team is working to restore the data to its original state.
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
2Stream in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
1
Median duration
2 h 33 min
This incident
1.6× the median
Other Stream incidents
All incidentsFollow 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.
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.cc/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.
https://outages.cc/feed.xml?providers=stream/feed subscribe https://outages.cc/feed.xml?providers=streamFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane