Stream Outage History

The Stream Chat API service in the Dublin region experienced a high error rate, leading to unreliable chat-related endpoints for users in that area. The issue began at Feb 11, 2026 8:13 AM UTC and progressed to a mitigation state as engineers worked on a fix. A solution was implemented by 9:13 AM UTC and monitoring continued, with services returning to normal later that day. The incident was resolved by 7:18 PM UTC, after roughly 11 hours. The provider issued 3 status updates during the incident to communicate updates and recovery progress. The impact was geographically limited to the Dublin region, affecting the Chat API in Dublin.

Stream experienced a brief outage in the Ohio region due to elevated API errors on Feed v3 and Chat. The affected components were Chat / ohio and Video / Joining Calls, causing degraded chat and video joining experiences for users in that area. The incident began when the status page moved to warning at 7:03 PM UTC and was resolved by 7:23 PM UTC, for an approximate duration of 20 minutes. The provider issued two status updates during the event, noting the elevated API errors and later confirming resolution, with services returning to normal after the incident. The issue appeared localized to the Ohio region with no reported global impact.

Stream carried out scheduled maintenance of the storage layer in the US-East region, during which the Chat / us-east and Video / Joining Calls components were placed in maintenance mode. The maintenance window began at 8:00 AM UTC and the status changed to maintenance at 8:03 AM UTC. The maintenance concluded at 9:33 AM UTC, with services returning to normal after a total duration of approximately 1 hour 33 minutes.

The provider issued 2 status updates during the incident, and the impact was geographically limited to the US-East region, affecting two components: Chat / us-east and Video / Joining Calls.

Stream carried out scheduled maintenance on the storage layer in the Mumbai region. During the window, the Chat / mumbai and Video / Joining Calls components were listed as in maintenance, which could have temporarily affected chat and video call functionality. The maintenance ran from Nov 4, 2025 11:03 PM UTC to Nov 5, 2025 12:33 AM UTC, lasting about 1 hour 30 minutes, and the Stream status page issued two updates to document the work and its completion. The geographic scope was regional to Mumbai with no broader impact indicated.

Stream conducted scheduled maintenance on the storage layer in the Ohio region, impacting two components: Chat / ohio and Video / Joining Calls. Users in Ohio may have experienced intermittent connectivity or degraded functionality during the maintenance window.

Maintenance began at 8:03 AM UTC and was completed by 9:33 AM UTC, following a planned window that started at 8:00 AM UTC. The Stream status page documented the in-progress maintenance and a restoration update, with two status updates issued during the incident. The regional impact was limited to the Ohio region, with affected components returning to normal after the maintenance window.

Stream performed a mandatory upgrade to the storage layer for the Chat component in the us-east (N. Virginia) region. The maintenance window ran from Oct 21, 2025 8:03 AM UTC to Oct 21, 2025 10:03 AM UTC, lasting about two hours. During this period, the Chat service in us-east was placed in maintenance mode, and the status page indicated the maintenance was in progress.

The Stream dashboard experienced intermittent availability lasting about 13 hours and 20 minutes, beginning at 4:58 PM UTC. The issue was linked to a global AWS outage that started around 4:56 PM UTC, impacting access to the Stream dashboard.

Stream's status page documented the progression, moving from Investigating to a degraded state and finally back to Up, with the dashboard restored at 6:18 AM UTC. The incident included two official status updates during its course.

An outage in the Stream Ohio region caused degraded performance across Chat API and related video services. The incident began at 7:38 PM UTC with a high error rate on the Chat API in Ohio, and affected additional components including Video / Joining Calls, Video / Recordings, and Video / Transcriptions. The outage lasted about 10 minutes, with services returning to normal by 7:48 PM UTC. The issue was caused by a problem with a shard's underlying database storage in the Ohio region. The provider issued two status updates during the incident describing the storage issue and ongoing restoration, and the geographic impact was limited to the Ohio region.

Stream experienced a brief degradation impacting the Chat and Feed APIs in the US-East region. Users may have encountered errors or slower responses when using chat and feed-related features. The issue was isolated to US-East and to the Chat and Feed components, with no global outage reported.

According to Stream's status updates, the degradation began around 3:53 PM UTC and lasted about 1 minute, with services restored by 3:54 PM UTC. The US-East Chat and Feed components moved from up to degraded temporarily, and the status returned to normal by Sep 3, 2025 4:03 PM UTC. The provider posted 2 updates during the incident.

Stream conducted a scheduled maintenance window on the Dublin storage layer that affected the Chat / Dublin component. The maintenance began around 12:30 AM UTC and the status page shows the transition to maintenance at 12:33 AM UTC. The Dublin region may have experienced intermittent access during this window. Updates on the status page indicated the maintenance was in progress and that additional updates would be provided as necessary.

At 4:33 AM UTC the Chat / Dublin component returned to normal operation and the status was updated to up. The maintenance lasted roughly 4 hours. The Stream status page issued 2 updates during the incident, describing the ongoing maintenance and the resolution. The impact was localized to the Dublin storage layer with no broader regional effects.