Elevated API Errors
The servers have returned operational.
Home
/
Status
/
Service
Communication API platform for enhanced user journey with AI capabilities.
Source
auto
Category
Communication
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 9m ago
2
Components
0
Active incidents
0
Maintenance
20%
90d uptime
Elevated API Errors
May 11, 6:46 AM
Normalized official status-page data for incidents, maintenance, components, and history.
20%
Known uptime
5 known history days
2
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
6
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Sendbird N Virginia 1 Desk Server
Operational
Sendbird N Virginia 1 server
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
4
outage days
0
maintenance days
85
unknown days
Latest outages and degradations detected from the official status page.
The servers have returned operational.
The servers have returned operational.
The servers have returned operational.
The servers have returned operational.
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
The servers have returned operational.
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.
The servers have returned operational.
The servers have returned operational.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Sendbird status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status-nvirginia1.sendbird.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 2 of 2 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Sendbird N Virginia 1 server | Operational | Component | Not recorded |
Sendbird N Virginia 1 Desk Server | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Sendbird is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.