Stream 中断历史

1. 2026年8月27日 UTC 05:25identified

   这一问题已经确定,一个解决办法正在实施之中.

2. 2026年8月27日 UTC 05:52monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年8月27日 UTC 06:22resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月5日 UTC 17:05investigating

   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日 UTC 21:08identified

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

3. 2026年8月5日 UTC 21:14resolved

   The incident has been resolved.

1. 2026年7月3日 UTC 06:28identified

   我们正经历一个高水平的API错误,目前正在研究这个问题.

2. 2026年7月3日 UTC 07:59resolved

   此事已决.

自动翻译自官方事件更新。

1. 2026年3月12日 UTC 13:33investigating

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

2. 2026年3月12日 UTC 14:17resolved

   This incident has been resolved.

1. 2026年3月12日 UTC 08:31investigating

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

2. 2026年3月12日 UTC 08:46identified

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

3. 2026年3月12日 UTC 09:26resolved

   This incident has been resolved.

1. 2026年2月11日 UTC 08:09identified

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

2. 2026年2月11日 UTC 09:10monitoring

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

3. 2026年2月11日 UTC 19:16resolved

   This incident has been resolved.

1. 2025年12月2日 UTC 19:01identified

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

2. 2025年12月2日 UTC 19:19monitoring

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

3. 2025年12月2日 UTC 20:19resolved

   This incident has been resolved.

1. 2025年11月11日 UTC 17:18resolved

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

1. 2025年10月20日 UTC 16:56investigating

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

2. 2025年10月21日 UTC 06:17resolved

   This incident has been resolved.

1. 2025年9月23日 UTC 19:38identified

   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日 UTC 19:44monitoring

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

3. 2025年9月23日 UTC 19:47resolved

   This incident has been resolved.

1. 2025年9月3日 UTC 15:48monitoring

   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日 UTC 15:58resolved

   This incident has been resolved.

1. 2025年7月30日 UTC 04:47monitoring

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

2. 2025年7月30日 UTC 08:21resolved

   This incident has been resolved.

1. 2025年5月16日 UTC 09:52resolved

   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日 UTC 19:25identified

   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日 UTC 21:02monitoring

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

3. 2025年4月16日 UTC 21:17resolved

   This incident has been resolved.

1. 2025年3月31日 UTC 13:39monitoring

   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日 UTC 17:48resolved

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

1. 2025年3月1日 UTC 19:03identified

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

2. 2025年3月1日 UTC 19:05identified

   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日 UTC 19:18resolved

   This incident has been resolved.

1. 2025年2月24日 UTC 12:02identified

   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日 UTC 14:27resolved

   The incident has been resolved.

1. 2025年1月20日 UTC 09:32identified

   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日 UTC 12:26resolved

   This incident has been resolved.

1. 2024年5月29日 UTC 01:06investigating

   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日 UTC 01:07resolved

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

1. 2024年5月9日 UTC 13:51investigating

   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日 UTC 13:52identified

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

3. 2024年5月9日 UTC 14:38resolved

   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.