Stream の障害履歴

1. 2026年8月27日 5:25 UTCidentified

   問題が特定され、修正が実装されています.

2. 2026年8月27日 5:52 UTCmonitoring

   修正を実装し、結果を監視しています.

3. 2026年8月27日 6:22 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月5日 17:05 UTCinvestigating

   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. 2026年8月5日 21:08 UTCidentified

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

3. 2026年8月5日 21:14 UTCresolved

   The incident has been resolved.

1. 2026年7月3日 6:28 UTCidentified

   高度な API エラーが発生し、現在問題を探しています.

2. 2026年7月3日 7:59 UTCresolved

   事件が解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年3月12日 13:33 UTCinvestigating

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

2. 2026年3月12日 14:17 UTCresolved

   This incident has been resolved.

1. 2026年3月12日 8:31 UTCinvestigating

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

2. 2026年3月12日 8:46 UTCidentified

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

3. 2026年3月12日 9:26 UTCresolved

   This incident has been resolved.

1. 2026年2月11日 8:09 UTCidentified

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

2. 2026年2月11日 9:10 UTCmonitoring

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

3. 2026年2月11日 19:16 UTCresolved

   This incident has been resolved.

1. 2025年12月2日 19:01 UTCidentified

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

2. 2025年12月2日 19:19 UTCmonitoring

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

3. 2025年12月2日 20:19 UTCresolved

   This incident has been resolved.

1. 2025年11月11日 17:18 UTCresolved

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

1. 2025年10月20日 16:56 UTCinvestigating

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

2. 2025年10月21日 6:17 UTCresolved

   This incident has been resolved.

1. 2025年9月23日 19:38 UTCidentified

   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. 2025年9月23日 19:44 UTCmonitoring

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

3. 2025年9月23日 19:47 UTCresolved

   This incident has been resolved.

1. 2025年9月3日 15:48 UTCmonitoring

   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. 2025年9月3日 15:58 UTCresolved

   This incident has been resolved.

1. 2025年7月30日 4:47 UTCmonitoring

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

2. 2025年7月30日 8:21 UTCresolved

   This incident has been resolved.

1. 2025年5月16日 9:52 UTCresolved

   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.

1. 2025年4月16日 19:25 UTCidentified

   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. 2025年4月16日 21:02 UTCmonitoring

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

3. 2025年4月16日 21:17 UTCresolved

   This incident has been resolved.

1. 2025年3月31日 13:39 UTCmonitoring

   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. 2025年3月31日 17:48 UTCresolved

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

1. 2025年3月1日 19:03 UTCidentified

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

2. 2025年3月1日 19:05 UTCidentified

   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. 2025年3月1日 19:18 UTCresolved

   This incident has been resolved.

1. 2025年2月24日 12:02 UTCidentified

   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. 2025年2月24日 14:27 UTCresolved

   The incident has been resolved.

1. 2025年1月20日 9:32 UTCidentified

   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. 2025年1月24日 12:26 UTCresolved

   This incident has been resolved.

1. 2024年5月29日 1:06 UTCinvestigating

   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. 2024年5月29日 1:07 UTCresolved

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

1. 2024年5月9日 13:51 UTCinvestigating

   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. 2024年5月9日 13:52 UTCidentified

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

3. 2024年5月9日 14:38 UTCresolved

   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.