Stream

Affected: us-east, US East, Edge network, Joining Calls, us-east, Recordings, Transcriptions, Broadcasting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-27 05:25 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-08-27 05:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-27 06:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 17:05 UTC

   We are aware of an issue affecting data retrieval for a subset of Chat customers located in the US-East region. Affected customers may see errors or empty results when retrieving messages from channels. Our engineering team is investigating.

2. identified 2026-08-05 21:08 UTC

   The issue has been identified, and our engineering team is working to restore the data to its original state.

3. resolved 2026-08-05 21:14 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Joining Calls, Recordings, singapore

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-03 06:28 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2026-07-03 07:59 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east, Joining Calls, us-east

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 13:33 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2026-03-12 14:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east, Joining Calls, us-east

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 08:31 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. identified 2026-03-12 08:46 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-12 09:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: dublin

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-11 08:09 UTC

   We're experiencing an elevated level of API errors and our team is currently working on a mitigation.

2. monitoring 2026-02-11 09:10 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-11 09:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: ohio, Joining Calls

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-02 19:01 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. monitoring 2025-12-02 19:19 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-12-02 20:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-11 17:18 UTC

   We identified an issue with sending messages. The issue is resolved. We're looking into the root cause

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 16:56 UTC

   We're currently investigating an issue with Stream's dashboard. The issue is caused by an outage of AWS.

2. resolved 2025-10-21 06:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: ohio, Joining Calls, Recordings, Transcriptions

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-23 19:38 UTC

   One of our shards in the ohio region is experiencing an issue with the underlying database storage. Our team is actively working to restore the service.

2. monitoring 2025-09-23 19:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-09-23 19:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east, us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-09-03 15:48 UTC

   We experienced a brief service degradation in some shards in the US-East region. The issue lasted for 1 minute and has since been resolved. Our team is currently monitoring the situation.

2. resolved 2025-09-03 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: singapore

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-30 04:47 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2025-07-30 08:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-16 09:27 UTC

   There was a significant spike in requests that hit one of our Edge shards in the US-East region, leading to an exhaustion of resources. The incident lasted 4 minutes.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-04-16 19:25 UTC

   One of our shards in the us-east region is experiencing an issue with the underlying database storage. Our team is actively working to restore the service.

2. monitoring 2025-04-16 21:02 UTC

   The issue is being resolved, and our team is closely monitoring the database.

3. resolved 2025-04-16 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Joining Calls

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-03-31 13:39 UTC

   Between 12:35 and 12:51 UTC, our API layer experienced a downtime in the Mumbai region due to increased system load. We are currently investigating the incident and implementing a patch. During this time API requests to join calls returned a 5xx response.

2. resolved 2025-03-31 17:48 UTC

   Our team deployed a patch to the affected system and the incident has been resolved

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-03-01 19:03 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2025-03-01 19:05 UTC

   One of our shards in the US-East region is experiencing degraded performance due to an issue with the underlying data storage. Our team is currently working on resolving the incident.

3. resolved 2025-03-01 19:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: dublin

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-02-24 12:02 UTC

   One of our shards in the Dublin region is experiencing degraded performance due to an issue with the underlying data storage. Our team is currently working on resolving the incident.

2. resolved 2025-02-24 14:27 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-01-20 09:32 UTC

   APIs are partially unreachable for users within the UAE on the DU Telecom and Virgin Telecom ISPs. Our team is currently working to remediate the problem by talking to the ISP and local authorities, a temporary remediation is also in progress.

2. resolved 2025-01-24 12:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: ohio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-29 01:06 UTC

   Our monitoring system has detected an incident affecting one of our shard in Ohio. Customers located on that shard have experienced a high error rate.

2. resolved 2024-05-29 01:07 UTC

   The incident has been resolved, and traffic is now served without any issue.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-09 13:51 UTC

   We are currently experiencing a high error rate on one of our Feed shards in the us-east region. Our team is actively working to resolve the situation.

2. identified 2024-05-09 13:52 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2024-05-09 14:38 UTC

   The shard has been recovered and the incident has been resolved. Our team is currently conducting an internal investigation to determine the root cause of the issue.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-04-29 19:42 UTC

   At 21:02 CET, a high error rate was recorded on the Chat API endpoints in one of our us-east shards. Our team resolved the issue at 21:18 CET, and the service is now operating normally.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east, dublin

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-03-28 11:30 UTC

   An issue with the QueryChannel endpoint led to some queries returning HTTP 403 response code. This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Personalization

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-09 07:32 UTC

   We are currently investigating an issue with our Feed Realtime service.

2. identified 2023-05-09 07:35 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2023-05-09 08:08 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2023-05-09 08:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-03-27 14:35 UTC

   The issue has been identified and our team is working on a remediation

2. resolved 2023-03-27 15:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: dublin

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-03-21 16:56 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2023-03-21 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Ohio

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2022-07-28 18:27 UTC

   We experience a partial outage due to AWS connectivity issues for selected apps in the Ohio region

2. identified 2022-07-28 18:36 UTC

   The issue has been resolved and the service in Ohio region is operating normally.

3. resolved 2022-07-28 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-12-08 07:20 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue. This issue affects one shard only in our us-east region.

2. identified 2021-12-08 08:55 UTC

   The issue has been identified and a fix is being implemented. A temporary remediation has been put in place to mitigate the ongoing issue.

3. monitoring 2021-12-08 09:02 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2021-12-08 11:04 UTC

   The issue of this morning propagated to an additional component of our infrastructure intended to dispatch messages to the end users via websocket protocol. Our team tried to mitigate the issue and the problem seems to be resolved now. We are still monitoring the situation...

5. resolved 2021-12-08 12:43 UTC

   The incident has been resolved. A post-mortem will follow.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2021-08-31 21:30 UTC

   Traffic to our Dublin infrastructure experienced elevated error rate due to a AWS outage. The incident started at 11:20PM, error rate decreased at 11:38PM and the incident was resolved by 11:59PM We are still performing impact and root-cause analysis, a postmortem with more...

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2021-04-14 05:30 UTC

   We experienced higher than normal error rates during a database maintenance on Chat API. The error increased started at 5:24AM and resolved at 5:42AM UTC.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2021-03-15 18:30 UTC

   High error rate on Chat HTTP APIs

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Personalization

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2021-01-06 05:00 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2021-01-06 09:53 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2021-01-06 10:02 UTC

   Realtime updates for feeds are back to normal, we are still monitoring the traffic. The previous patch unfortunately did not resolve the problem and was causing realtime clients to retry the connection via the `Client not found, please reconnect` response.

4. resolved 2021-01-06 15:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Personalization

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2021-01-04 16:57 UTC

   We are currently investigating an issue with AWS SQS, we are receiving 100% error rate from SQS APIs. Our feeds realtime endpoint is currently unable to push notifications to SQS.

2. monitoring 2021-01-04 17:38 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2021-01-04 19:45 UTC

   We are continuing to monitor for any further issues.

4. resolved 2021-01-04 23:25 UTC

   Millions of requests to the handshake endpoint of our feed realtime system broke the API. This issue has been resolved and a full post mortem will follow.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-12-09 16:59 UTC

   We are currently investigating an increase of errors on Chat API

2. identified 2020-12-09 17:20 UTC

   We identified an issue with Chat API that caused some messages to not being delivered via Websockets. The problem is already resolved for most applications, and the remediation should be completed for all apps shortly.

3. resolved 2020-12-09 17:43 UTC

   This incident has been resolved.

4. postmortem 2020-12-10 20:36 UTC

   We have completed the post mortem for the December 9th incident. As the founder and CEO of Stream I’d like to apologize to all of our customers impacted by this issue. Stream powers activity feeds and chat for a billion end users, and we recognize that our customers operating in...

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east, us-east

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2020-07-28 10:37 UTC

   Due to a networking issue on AWS us-east region, we are experiencing increased latency for some of the traffic on our US region. We are mitigating the problem while waiting for a final remediation on AWS infrastructure.

2. resolved 2020-07-28 12:12 UTC

   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.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2020-01-28 16:12 UTC

   A recent released caused load increase on part of the chat infrastructure and caused degraded performance and timeout errors. Remediation is in progress.

2. monitoring 2020-01-28 16:45 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2020-01-28 16:57 UTC

   We are continuing to monitor for any further issues.

4. resolved 2020-01-28 16:58 UTC

   This incident has been resolved.

5. postmortem 2020-01-28 16:59 UTC

   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...

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2019-11-21 21:27 UTC

   We are experiencing spikes of timeout errors; the team is investigating on the root cause and working on a remediation

2. monitoring 2019-11-21 22:04 UTC

   Increased load on some API endpoints caused traffic to spike intermittently. Adding more capacity remediated the problem.

3. resolved 2019-11-21 22:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2019-08-30 14:46 UTC

   Emails from Dashboard (invites, password resets and other notifications are currently not sent correctly). We are talking to our SMTP provider (Mailgun) to resolve this issue as soon as possible.

2. resolved 2019-08-30 16:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Dashboard

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-05-10 20:40 UTC

   The dashboard has a bug that's causing it to redirect some users to the homepage. Our team is investigating. APIs are fully operational, this only impacts the dashboard.

2. resolved 2019-05-10 21:34 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2019-02-06 14:23 UTC

   We were experiencing an elevated level of API errors on our us-east region. This incident lasted from 2:11PM UTC to 2:18PM.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2019-01-02 13:04 UTC

   We were experiencing an elevated level of API errors because of a Redis upgrade that was unsuccessful. We have resolved the issue and are monitoring for further problems

2. resolved 2019-01-02 13:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A zone, region or data center became unavailable. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2018-11-22 13:08 UTC

   Due to an operation mistake, API service between 12:56PM UTC and 12:58PM UTC API had very high error rate on the Europe West region. The problem is mitigated and resolved. Detailed API error rate over time: 12:56PM 78% 12:57PM 93% 12:58PM 4%

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2018-08-23 15:59 UTC

   Between 03:59PM and 04:32PM UTC API traffic resulted in HTTP errors or timeouts. Only a part of Stream applications hosted on US were affected by this problem.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Personalization

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2018-08-08 01:09 UTC

   Our distributed realtime cluster uses Redis (on Elasticache) for state management. A failover of the Elasticache cluster caused realtime to be unavailable for 7 minutes. This issue has been resolved and we're investigating why the failover took 7 minutes. This impacted customers...

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: Personalization

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2018-06-21 18:02 UTC

   Connections are back, currently investigating the root cause.

Excerpts are shortened. Read the full incident on Stream's status page.

Affected: us-east

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2018-04-26 07:49 UTC

   Between 7:24AM and 7:26AM UTC we had an increased error rate due to a database failover procedure triggered by AWS.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2018-04-13 13:33 UTC

   We experienced an elevated rate of API errors between 13:00 and 13:01 UTC. The issue resolved itself and we are looking into the cause.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2018-03-14 15:07 UTC

   We're currently investigating problems with loading the Dashboard.

2. monitoring 2018-03-14 15:38 UTC

   The CDN (IMGIX) is not serving static files from our origin correctly (https://status.imgix.com/incidents/5plz9dqxxhns). We have temporarily mitigated the problem by rolling back to a previous release (the statics for that release are available at CDN edge nodes and are returned...

3. resolved 2018-03-14 15:51 UTC

   We switched to our back-up CDN a few minutes ago. Dashboard is fully operation again.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2018-02-14 10:19 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. monitoring 2018-02-14 10:22 UTC

   The issue seems to be resloved

3. resolved 2018-02-14 10:37 UTC

   The outage started 10:14 UTC and was over at 10:18 UTC.

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2018-02-03 18:46 UTC

   A small part of Stream's customers was impacted by an issue that caused notification feeds to be temporarily unavailable. Earlier today at 15:30 GMT a maintenance database migration was initiated; unfortunately the procedure did not clear the cached state of feeds correctly....

Excerpts are shortened. Read the full incident on Stream's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2018-01-24 12:09 UTC

   Between 11:43 UTC and 11:47 API traffic had a spike in HTTP 5xx errors and an increase of latency.

2. postmortem 2018-07-30 19:30 UTC

   ### January 23 and 24 outage postmortem report Stream suffered two incidents of degraded performance in the past 24 hours. We take uptime very seriously, and would like to be transparent with our operations and to our customers. The spikes occurred on Jan 23 at 3:50PM UTC and on...

Excerpts are shortened. Read the full incident on Stream's status page.