Stream
Stream is operational
Checked Operational
User reports
What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Stream status page.
No reviewed reports in the last 24 hours.
History
90 days agoToday
outages.live tracks Stream since . The days before that show only what Stream published.
Incidents in 90 days
2
Days with an incident
1
Median duration
2 h 33 min
Longest incident
4 h 9 min
Components
33Additional services
Dashboard Operational
90 days agoNo incidentsToday
CDN Operational
90 days agoNo incidentsToday
Feed
Personalization Operational
90 days agoNo incidentsToday
Realtime Operational
90 days agoNo incidentsToday
us-east Operational
90 days ago1 day with an incidentToday
dublin Operational
90 days agoNo incidentsToday
mumbai Operational
90 days agoNo incidentsToday
singapore Operational
90 days agoNo incidentsToday
tokyo Operational
90 days agoNo incidentsToday
Chat
us-east Operational
90 days ago1 day with an incidentToday
ohio Operational
90 days agoNo incidentsToday
dublin Operational
90 days agoNo incidentsToday
mumbai Operational
90 days agoNo incidentsToday
singapore Operational
90 days agoNo incidentsToday
sydney Operational
90 days agoNo incidentsToday
london Operational
90 days agoNo incidentsToday
canada Operational
90 days agoNo incidentsToday
API Edge Network
US East Operational
90 days ago1 day with an incidentToday
Ohio Operational
90 days agoNo incidentsToday
Canada Operational
90 days agoNo incidentsToday
Brazil (saõ paulo) Operational
90 days agoNo incidentsToday
Dublin Operational
90 days agoNo incidentsToday
Frankfurt Operational
90 days agoNo incidentsToday
Mumbai Operational
90 days agoNo incidentsToday
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=streamSlack
/feed subscribe https://outages.live/feed.xml?providers=streamGo from tracking outages to fixing production issues with Polylane.
Try Polylane