Histórico de interrupções do Sendbird

1. 25 Here 2026 da 05:05 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 25 Here 2026 da 05:07 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Here 2026 da 22:50 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 9 Here 2026 da 22:51 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Here 2026 da 22:35 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 9 Here 2026 da 22:39 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Here 2026 da 22:16 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 9 Here 2026 da 22:30 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gwengolo 2026 da 15:08 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 29 Gwengolo 2026 da 15:13 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gwengolo 2026 da 18:17 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 24 Gwengolo 2026 da 18:26 UTCresolved

   Entre 14:15 e 14:26 EDT em 24 de setembro, verificações de saúde automatizadas para várias regiões de Sendbird hospedadas nos EUA desencadearam alertas devido a um problema com nosso sistema de monitoramento. Os serviços Sendbird permaneceram totalmente operacionais durante esse período, sem impacto em conexões, mensagens ou pedidos de API. A questão da monitorização resolveu-se automaticamente, e todos os controlos de saúde permaneceram normais desde então. Nenhuma ação do cliente é necessária.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Eost 2026 da 09:04 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 3 Eost 2026 da 09:13 UTCresolved

   Os servidores voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Mae 2026 da 06:46 UTCinvestigating

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

2. 11 Mae 2026 da 06:53 UTCresolved

   The servers have returned operational.

1. 15 Ebrel 2026 da 00:01 UTCinvestigating

   We are currently investigating this issue.

2. 15 Ebrel 2026 da 00:59 UTCresolved

   The servers have returned operational.

1. 13 Ebrel 2026 da 08:15 UTCinvestigating

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

2. 13 Ebrel 2026 da 08:28 UTCresolved

   The servers have returned operational.

1. 31 Meurzh 2026 da 17:42 UTCinvestigating

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

2. 31 Meurzh 2026 da 17:43 UTCresolved

   The servers have returned operational.

1. 3 Meurzh 2026 da 07:38 UTCidentified

   Impact: Full outage, all requests failed

2. 3 Meurzh 2026 da 08:46 UTCresolved

   When: 2026-03-03 06:43 – 08:02 (UTC) Impact: Full outage, all requests failed Root cause: Unexpected issue following a Redis security (TLS) configuration change Immediate remediation: Provisioned a new secure Redis cluster and migrated traffic; service fully restored and operating normally

1. 1 Kerzu 2025 da 05:42 UTCinvestigating

   We are currently investigating this issue.

2. 1 Kerzu 2025 da 05:46 UTCresolved

   The servers have returned operational.

1. 19 Du 2025 da 08:47 UTCinvestigating

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

2. 19 Du 2025 da 08:48 UTCresolved

   The servers have returned operational.

1. 13 Du 2025 da 17:21 UTCresolved

   Earlier today, we observed unexpected behavior within our chat service infrastructure that affected websocket stability. A subset of websocket server pods entered a state where they were unable to restart normally, which increased load on the remaining healthy pods. Over time, this imbalance led to elevated memory usage and eventually caused some pods to reach OOM (Out of Memory) conditions. As these pods became unavailable, a significant number of websocket connections dropped simultaneously at approximately 07:00 PT. Our team took action to stabilize the environment and completed a rollback to a previously stable server version at 08:30 PT, after which system performance and connection reliability returned to normal. We continue to investigate the underlying cause to prevent recurrence.

1. 20 Here 2025 da 20:13 UTCinvestigating

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

2. 20 Here 2025 da 20:18 UTCresolved

   The servers have returned operational.

1. 20 Here 2025 da 20:01 UTCinvestigating

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

2. 20 Here 2025 da 20:05 UTCresolved

   The servers have returned operational.

1. 20 Here 2025 da 19:23 UTCinvestigating

   As of 12:05 pm PST services on the region are impacted. We are investigating the root cause. Updates will be provided as available

2. 20 Here 2025 da 20:47 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 17:33 UTCinvestigating

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

2. 20 Here 2025 da 17:38 UTCresolved

   The servers have returned operational.

1. 20 Here 2025 da 16:32 UTCinvestigating

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

2. 20 Here 2025 da 17:32 UTCresolved

   The servers have returned operational.