Sendbird Outage History
Sendbird is up right nowPingoru has recorded 53 incidents for Sendbird: 14 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 1 of 720 (0%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 2 | 0 of 720 (0%) |
| October 2026 | 3 | 0 of 566 (0%) |
Incidents, newest first
Critical October 9, 2026 Elevated API Errors 1m Sendbird N Virginia 1 server
Started Oct 09, 2026, 10:50 PM UTC· resolved Oct 09, 2026, 10:51 PM UTC
- investigating Oct 09, 2026, 10:50 PM UTC
We're experiencing an elevated level of API errors and are currently looking into the issue.
- resolved Oct 09, 2026, 10:51 PM UTC
The servers have returned operational.
Critical September 29, 2026 Increased Error Rates (Sendbird Desk) 5m Sendbird N Virginia 1 Desk Server
Started Sep 29, 2026, 03:08 PM UTC· resolved Sep 29, 2026, 03:13 PM UTC
- investigating Sep 29, 2026, 03:08 PM UTC
We are currently investigating this issue.
- resolved Sep 29, 2026, 03:13 PM UTC
The servers have returned operational.
Critical March 3, 2026 Full outage 1h 7m Sendbird N Virginia 1 server, Sendbird N Virginia 1 Desk Server
Started Mar 03, 2026, 07:38 AM UTC· resolved Mar 03, 2026, 08:46 AM UTC
- identified Mar 03, 2026, 07:38 AM UTC
Impact: Full outage, all requests failed
- resolved Mar 03, 2026, 08:46 AM UTC
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
Major November 13, 2025 Dropped websocket connections –
Started Nov 13, 2025, 03:00 PM UTC· resolved Nov 13, 2025, 03:00 PM UTC
- resolved Nov 13, 2025, 05:21 PM UTC
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.
Critical October 20, 2025 Service outage 1h 24m Sendbird N Virginia 1 server, Sendbird N Virginia 1 Desk Server
Started Oct 20, 2025, 07:23 PM UTC· resolved Oct 20, 2025, 08:47 PM UTC
- investigating Oct 20, 2025, 07:23 PM UTC
As of 12:05 pm PST services on the region are impacted. We are investigating the root cause. Updates will be provided as available
- resolved Oct 20, 2025, 08:47 PM UTC
This incident has been resolved.
Critical August 26, 2025 Increased Error Rates 4m Sendbird N Virginia 1 Desk Server
Started Aug 26, 2025, 04:49 AM UTC· resolved Aug 26, 2025, 04:54 AM UTC
- investigating Aug 26, 2025, 04:49 AM UTC
We are currently investigating this issue.
- resolved Aug 26, 2025, 04:54 AM UTC
The servers have returned operational.
Major March 6, 2025 Partial Outage – Sendbird N Virginia 1 server
Started Mar 06, 2025, 05:58 AM UTC· resolved Mar 06, 2025, 05:58 AM UTC
- resolved Mar 06, 2025, 05:58 AM UTC
When: 2025-03-06 05:04:00 - 05:16:00 UTC Impact: Partial connections errors for new websocket requests Cause: A configuration of this specific region was not applied appropriately, and new connections could not be made during this time Remediation: Rolled back the problematic config
Critical October 29, 2024 Bot is not responding intermittently 1m
Started Oct 29, 2024, 01:46 AM UTC· resolved Oct 29, 2024, 01:47 AM UTC
- investigating Oct 29, 2024, 01:46 AM UTC
We're experiencing an elevated level of errors and are currently looking into the issue.
- resolved Oct 29, 2024, 01:47 AM UTC
The Chatbot servers have returned operational.