Sendbird Oregon Outage History

Sendbird Oregon is up right now

Sendbird Oregon had 4 outages in the last 2 years totaling 24h 16m of downtime — averaging 0.2 incidents per month.

There were 4 Sendbird Oregon outages since August 14, 2025 totaling 24h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Critical April 15, 2026

Increased Error Rates (Sendbird Desk)

Detected by Pingoru
Apr 15, 2026, 02:01 AM UTC
Resolved
Apr 15, 2026, 02:09 AM UTC
Duration
8m
Affected: Sendbird Oregon Desk Server
Timeline · 2 updates
  1. investigating Apr 15, 2026, 02:01 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 15, 2026, 02:09 AM UTC

    The servers have returned operational.

Read the full incident report →

Critical January 28, 2026

Elevated API Errors

Detected by Pingoru
Jan 28, 2026, 05:22 PM UTC
Resolved
Jan 28, 2026, 05:26 PM UTC
Duration
3m
Affected: Sendbird Oregon server
Timeline · 2 updates
  1. investigating Jan 28, 2026, 05:22 PM UTC

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

  2. resolved Jan 28, 2026, 05:26 PM UTC

    The servers have returned operational.

Read the full incident report →

Critical December 1, 2025

Increased Error Rates

Detected by Pingoru
Dec 01, 2025, 05:45 AM UTC
Resolved
Dec 01, 2025, 05:50 AM UTC
Duration
4m
Affected: Sendbird Oregon Desk Server
Timeline · 2 updates
  1. investigating Dec 01, 2025, 05:45 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 01, 2025, 05:50 AM UTC

    The servers have returned operational.

Read the full incident report →

Major October 13, 2025

Webhook delivery failures

Detected by Pingoru
Oct 13, 2025, 08:00 AM UTC
Resolved
Oct 14, 2025, 08:00 AM UTC
Duration
1d
Timeline · 1 update
  1. resolved Oct 14, 2025, 08:06 PM UTC

    Between 1:03 AM – 3:08 AM PT on October 14, 2025, webhook deliveries failed due to an infrastructure issue. The issue has been fully resolved, and webhook functionality has returned to normal.

Read the full incident report →