Sendbird Outage History

20 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Sendbird status98.76% uptime history

Every Recorded Sendbird Incident

Sendbird incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 3, 2026North Virginia, USA: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.3 minResolved
Aug 3, 2026Frankfurt, Germany: Increased Error Rates (Sendbird Desk)We are currently investigating this issue.3 minResolved
Jul 23, 2026Seoul, Korea: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.11 minResolved
Jul 23, 2026North Virginia 2, USA: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.1h 13mResolved
Jul 23, 2026Frankfurt, Germany: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.1h 13mResolved
Jul 2, 2026Seoul, Korea: Infrastructure maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.1h 11mResolved
Jul 1, 2026North Virginia 2, USA: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.12 minResolved
Jul 1, 2026North Virginia 2, USA: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.7 minResolved
Jul 1, 2026Seoul, Korea: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.50 minResolved
Jun 27, 2026North Virginia 2, USA: Infrastructure maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.1h 25mResolved
Jun 25, 2026North Virginia 2, USA: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.1h 28mResolved
Jun 22, 2026Sydney, Australia: Infrastructure MigrationScheduled maintenance is currently in progress. We will provide updates as necessary.1h 23mResolved
Jun 22, 2026Sydney, Australia: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.32 minResolved
Jun 16, 2026Frankfurt, Germany: System maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.1h 42mResolved
Jun 15, 2026Frankfurt, Germany: Increased Error Rates (Sendbird Desk)We are currently investigating this issue.48 minResolved
Jun 3, 2026North Virginia 2, USA: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.1 minResolved
Jun 1, 2026Seoul, Korea: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.0 minResolved
May 29, 2026Frankfurt, Germany: AI agent is not responding intermittentlyWe're experiencing an elevated level of errors and are currently looking into the issue.0 minResolved
May 27, 2026Frankfurt, Germany: Increased Error Rates (Sendbird Desk)We are currently investigating this issue.58 minResolved
May 19, 2026Seoul, Korea: Elevated API ErrorsWe're experiencing an elevated level of API errors and are currently looking into the issue.5 minResolved

How to Read This Sendbird Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sendbird acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Sendbird outage in this window ran 1h 42m, against a mean recovery of 40 min. If you depend on Sendbird in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.