Last checked: 4 minutes 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: DNS resolution for getstream.io is back to normal. The two .io name servers are now returning the correct results.
Status: Resolved
Impact: Major | Started At: Sept. 20, 2017, 2:08 p.m.
Description: We identified and resolved a problem affecting API latency for several applications. The problem was pinned down to heavy pressure on a Postgresql server, the issue was resolved and latency returned to normal levels.
Status: Resolved
Impact: None | Started At: July 21, 2017, 4:24 p.m.
Description: The problem was related to a routine maintenance slowing down query response times for one Postgresql database. The latency for API was impacted between 3:50PM and 4:15PM UTC.
Status: Resolved
Impact: Minor | Started At: May 1, 2017, 4:17 p.m.
Description: There was a temporary spike in latency caused by our Cassandra cluster. The issue has been mitigated.
Status: Resolved
Impact: None | Started At: April 4, 2017, 9:46 p.m.
Description: The high latency has now been resolved. The root cause isn't clear yet.
Status: Resolved
Impact: None | Started At: Feb. 24, 2017, 5: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.