Last checked: 18 seconds ago
Get notified about any outages, downtime or incidents for getstream.io and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for getstream.io.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Brazil (São Paulo) | Active |
Chat - Edge | Active |
Canada | Active |
Chat - Edge | Active |
Dublin | Active |
Chat - API | Active |
Chat - Edge | Active |
Feed - API | Active |
Frankfurt | Active |
Chat - Edge | Active |
Global services | Active |
CDN | Active |
Dashboard | Active |
Edge | Active |
Mumbai | Active |
Chat - API | Active |
Chat - Edge | Active |
Feed - API | Active |
Ohio | Active |
Chat - API | Active |
Chat - Edge | Active |
Singapore | Active |
Chat - API | Active |
Chat - Edge | Active |
Feed - API | Active |
South Africa (Cape Town) | Active |
Chat - Edge | Active |
Sydney | Active |
Chat - API | Active |
Chat - Edge | Active |
Tokyo | Active |
Chat - Edge | Active |
Feed - API | Active |
US-East | Active |
Chat - API | Active |
Chat - Edge | Active |
Feed - API | Active |
Feed - Personalization | Active |
Feed - Realtime notifications | Active |
View the latest incidents for getstream.io and check for official updates:
Description: AWS Networking issue is now resolved. We are now cleaning up our temporary remediations since they are not needed anymore. Traffic is back to normal for the last hour.
Status: Resolved
Impact: Minor | Started At: July 28, 2020, 10:37 a.m.
Description: Between 4:05PM and 4:45PM UTC on January 28 2020 we had an API outage caused by performance degradation. The event was triggered by a new release to our Chat API servers; quickly after the new release was live, load on our database infrastructure increased and caused HTTP response times to spike and time-out in some cases. The event was detected by our latency and error monitoring. The team started working on the event by rolling back to the previous version at 4:20PM UTC. Unfortunately the rollback did not resolve the problem entirely. After another rollback attempt we realised there were still pending queries from the previous release running on our PostgreSQL database. We manually terminated all the pending tasks at 4:40PM UTC; after that the error rate dropped to 0% again. The outage affected 5% of HTTP requests at its peak \(4:20PM to 4:27PM UTC\).
Status: Postmortem
Impact: Minor | Started At: Jan. 28, 2020, 4:12 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Nov. 21, 2019, 9:27 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: Aug. 30, 2019, 2:46 p.m.
Description: This issue has been resolved.
Status: Resolved
Impact: None | Started At: May 10, 2019, 8:40 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.