User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 214 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 78 ms | 0 |
| Mon 20 | 0 | 0.0 | 102 ms | 0 |
| Mon 23 | 0 | 0.0 | 180 ms | 0 |
| Tue 01 | 0 | 0.0 | 71 ms | 0 |
| Tue 03 | 0 | 0.0 | 118 ms | 0 |
| Tue 05 | 0 | 0.0 | 62 ms | 0 |
| Tue 07 | 0 | 0.0 | 71 ms | 0 |
| Tue 09 | 0 | 0.0 | 70 ms | 0 |
| Tue 11 | 0 | 0.0 | 89 ms | 0 |
| Tue 13 | 0 | 0.0 | 103 ms | 0 |
| Tue 16 | 0 | 0.0 | 73 ms | 0 |
| Tue 18 | 0 | 0.0 | 55 ms | 0 |
| Tue 20 | 0 | 0.0 | 144 ms | 0 |
| Tue 22 | 0 | 0.0 | 73 ms | 0 |
| Wed 01 | 0 | 0.0 | 91 ms | 0 |
| Wed 03 | 0 | 0.0 | 169 ms | 0 |
| Wed 05 | 0 | 0.0 | 43 ms | 0 |
| Wed 07 | 0 | 0.0 | 76 ms | 0 |
| Wed 10 | 0 | 0.0 | 69 ms | 0 |
| Wed 12 | 0 | 0.0 | 95 ms | 0 |
| Wed 14 | 0 | 0.0 | 81 ms | 0 |
| Wed 16 | 0 | 0.0 | 53 ms | 0 |
| Wed 18 | 0 | 0.0 | 129 ms | 0 |
| Wed 20 | 0 | 0.0 | 153 ms | 0 |
| Wed 23 | 0 | 0.0 | 154 ms | 0 |
| Thu 01 | 0 | 0.0 | 105 ms | 0 |
| Thu 03 | 0 | 0.0 | 55 ms | 0 |
| Thu 05 | 0 | 0.0 | 142 ms | 0 |
| Thu 07 | 0 | 0.0 | 74 ms | 0 |
| Thu 09 | 0 | 0.0 | 80 ms | 0 |
| Thu 11 | 0 | 0.0 | 609 ms | 0 |
| Thu 13 | 0 | 0.0 | 103 ms | 0 |
| Thu 15 | 0 | 0.0 | 220 ms | 0 |
| Thu 17 | 0 | 0.0 | 248 ms | 0 |
| Thu 19 | 0 | 0.0 | 102 ms | 0 |
| Thu 21 | 0 | 0.0 | 100 ms | 0 |
| Thu 23 | 0 | 0.0 | 188 ms | 0 |
| Fri 01 | 0 | 0.0 | 98 ms | 0 |
| Fri 02 | 0 | 0.0 | 185 ms | 0 |
| Fri 04 | 0 | 0.0 | 54 ms | 0 |
| Fri 06 | 0 | 0.0 | 49 ms | 0 |
| Fri 08 | 0 | 0.0 | 150 ms | 0 |
| Fri 10 | 0 | 0.0 | 179 ms | 0 |
| Fri 11 | 0 | 0.0 | 75 ms | 0 |
| Fri 13 | 0 | 0.0 | 647 ms | 0 |
| Fri 15 | 0 | 0.0 | 181 ms | 0 |
| Fri 17 | 0 | 0.0 | 100 ms | 0 |
| Fri 18 | 0 | 0.0 | 157 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for getstream.io yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when getstream.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send getstream.io alerts to Slack, Discord or a webhook — free.
getstream.io, at getstream.io, is one of the AI services we monitor. Stream provides APIs and SDKs for in-app chat, video calling, livestreaming, activity feeds and AI moderation. Trusted by 2,000+ apps. Start free.
getstream.io publishes an official status page at status.getstream.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 166 ms average, 49–647 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public getstream.io incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
166 ms on average over the last 24 hours (49–647 ms).
Yes, at https://status.getstream.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report getstream.io here at once, the problem is on getstream.io's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with getstream.io. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.