Service disruption in US-East
ResolvedOfficial update
This incident has been resolved.
The latest update from Stream.
State
Resolved
Started
Lasted
58 min
Worst impact
Major outage
Timeline
3 updates05:2505:3905:5306:0806:22
Major outageUpdate postedTimes in UTC
Identified
27 min 47%
Monitoring
30 min 53%
Updates
Times in UTCAs posted by Stream
Resolved
This incident has been resolved.
Monitoring
A fix has been implemented and we are monitoring the results.
Identified
The issue has been identified and a fix is being implemented.
Affected components
15us-eastUS EastEdge networkJoining CallsRecordingsTranscriptionsBroadcastingChat - us-east
Stream in the last 90 days
Full history90 days agoToday
Incidents in 90 days
2
Days with an incident
1
Median duration
2 h 33 min
This incident
62% shorter than 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.
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.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.
RSS
https://outages.cc/feed.xml?providers=streamSlack
/feed subscribe https://outages.cc/feed.xml?providers=streamFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane