Sendbird Seoul Outage History

Sendbird Seoul is up right now

Sendbird Seoul had 4 outages in the last 2 years totaling 34m of downtime — averaging 0.2 incidents per month.

There were 4 Sendbird Seoul outages since January 17, 2025 totaling 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status-seoul.sendbird.com

Critical September 14, 2026

Elevated API Errors

Detected by Pingoru
Sep 14, 2026, 07:47 PM UTC
Resolved
Sep 14, 2026, 07:50 PM UTC
Duration
3m
Affected: Sendbird Seoul server
Timeline · 2 updates
  1. investigating Sep 14, 2026, 07:47 PM UTC

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

  2. resolved Sep 14, 2026, 07:50 PM UTC

    The servers have returned operational.

Read the full incident report →

Critical September 14, 2026

Increased Error Rates (Sendbird Desk)

Detected by Pingoru
Sep 14, 2026, 07:08 AM UTC
Resolved
Sep 14, 2026, 07:14 AM UTC
Duration
5m
Affected: Sendbird Seoul Desk Server
Timeline · 2 updates
  1. investigating Sep 14, 2026, 07:08 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 14, 2026, 07:14 AM UTC

    The servers have returned operational.

Read the full incident report →

Critical November 11, 2025

Increased Error Rates

Detected by Pingoru
Nov 11, 2025, 03:58 AM UTC
Resolved
Nov 11, 2025, 04:03 AM UTC
Duration
5m
Affected: Sendbird Seoul Desk Server
Timeline · 2 updates
  1. investigating Nov 11, 2025, 03:58 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 11, 2025, 04:03 AM UTC

    The servers have returned operational.

Read the full incident report →

Notice January 17, 2025

Bot is not responding intermittently

Detected by Pingoru
Jan 17, 2025, 11:51 PM UTC
Resolved
Jan 18, 2025, 12:11 AM UTC
Duration
19m
Timeline · 2 updates
  1. investigating Jan 17, 2025, 11:51 PM UTC

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

  2. resolved Jan 18, 2025, 12:11 AM UTC

    The Chatbot servers have returned operational.

Read the full incident report →