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일 오후 5: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일 오후 9: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일 오후 9: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일 오후 1:33 UTCinvestigating

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

2. 2026년 3월 12일 오후 2: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일 오후 7:16 UTCresolved

   This incident has been resolved.

1. 2025년 12월 2일 오후 7:01 UTCidentified

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

2. 2025년 12월 2일 오후 7:19 UTCmonitoring

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

3. 2025년 12월 2일 오후 8:19 UTCresolved

   This incident has been resolved.

1. 2025년 11월 11일 오후 5:18 UTCresolved

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

1. 2025년 10월 20일 오후 4: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일 오후 7: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일 오후 7:44 UTCmonitoring

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

3. 2025년 9월 23일 오후 7:47 UTCresolved

   This incident has been resolved.

1. 2025년 9월 3일 오후 3: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일 오후 3: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일 오후 7: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일 오후 9:02 UTCmonitoring

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

3. 2025년 4월 16일 오후 9:17 UTCresolved

   This incident has been resolved.

1. 2025년 3월 31일 오후 1: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일 오후 5:48 UTCresolved

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

1. 2025년 3월 1일 오후 7:03 UTCidentified

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

2. 2025년 3월 1일 오후 7: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일 오후 7: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일 오후 2: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일 오후 1: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일 오후 1:52 UTCidentified

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

3. 2024년 5월 9일 오후 2: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.