Sendbird outage history

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

The servers have returned operational.

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

The servers have returned operational.

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

The servers have returned operational.

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

The servers have returned operational.

We are currently investigating this issue.

The servers have returned operational.

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

Between 14:15 and 14:26 EDT on September 24, automated health checks for several US-hosted Sendbird regions triggered alerts due to an issue with our monitoring system. Sendbird services remained fully operational during this period, with no impact to connections, messaging, or API requests. The monitoring issue resolved automatically, and all health checks have remained normal since. No customer action is required.

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

The servers have returned operational.

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

The servers have returned operational.

We are currently investigating this issue.

The servers have returned operational.

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

The servers have returned operational.

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

The servers have returned operational.

Impact: Full outage, all requests failed

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

We are currently investigating this issue.

The servers have returned operational.

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

The servers have returned operational.

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.

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

The servers have returned operational.

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

The servers have returned operational.

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

This incident has been resolved.

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

The servers have returned operational.

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

The servers have returned operational.