Loading status…
Stream status · Communication · checked (23s ago)
Also searched as GetStream, getstream.io.
No — Stream is not down. All Stream systems are reported operational.
According to Stream's official status page, Stream was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Stream's feed reported no outage in 99.94% of our checks.
Everything above is read from Stream's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Stream in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Stream (getstream.io) provides hosted chat and activity feed infrastructure — the messaging, feeds and moderation behind other companies' apps, delivered through SDKs and a realtime websocket connection.
Stream's status page reports by product and by region, which matters because chat clients hold a persistent websocket to a regional edge. The realtime connection and the REST API are separate components and fail separately: message history can load while live updates stop arriving.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Stream's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Stream was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 23s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Stream's status endpoint.
Stream has published 10 incidents in the last 12 months, newest first. Only what Stream posted itself — not every problem users hit.
resolved · Aug 27, 05:25 AM (24d ago)
resolved · Aug 5, 05:05 PM (45d ago)
resolved · Jul 3, 06:28 AM (78d ago)
resolved · Mar 12, 01:33 PM (191d ago)
resolved · Mar 12, 08:31 AM (191d ago)
resolved · Feb 11, 08:09 AM (220d ago)
resolved · Dec 2, 07:01 PM (291d ago)
resolved · Nov 11, 05:18 PM (312d ago)
resolved · Oct 20, 04:56 PM (334d ago)
resolved · Sep 23, 07:38 PM (361d ago)
If messages appear only after a refresh, the websocket has dropped and not reconnected — that is a client-side connection issue, often a proxy or a mobile network killing idle connections. Expired user tokens fail in a way that looks like a service outage. Permissions configured on the wrong channel type are a frequent cause of silently failing writes.
