Outages · APIs: messaging, media, analytics
Operational LiveKit Cloud outage dossier
livekit.io · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 14 minor
- 3 none
- 1 critical
- 2 major
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 51 minLiveKit Cloud dashboard unavailableminor resolved · Cloud Dashboard (cloud.livekit.io) · official notice ↗ · replay & discuss
- → resolved · lasted Elevated timeouts on LiveKit Inference Gemma 4 31B on low-priority requestsnone resolved · official notice ↗ · replay & discuss
- → resolved · lasted Disconnections and failed connections in multiple regionsminor postmortem · US East - Ingress, US West - Ingress, US West - Real Time Communication, US Central - Real Time Communication · official notice ↗ · replay & discuss
- → resolved · lasted 1.5 hInvestigating failing calls and RoomService API failures in US East and dashboard issuesminor postmortem · Cloud Dashboard (cloud.livekit.io), US East - SIP, US Central - SIP, US Central - Real Time Communication · official notice ↗ · replay & discuss
- → resolved · lasted 42 minIncreased join latency in US East and US Centralminor postmortem · US Central - Real Time Communication, US East - Real Time Communication · official notice ↗ · replay & discuss
- → resolved · lasted 32 minInvestigating reports of elevated API failures in Chicago regionminor postmortem · US Central - Real Time Communication · official notice ↗ · replay & discuss
- → resolved · lasted 1.4 hDegraded SIP Performance in US Westminor postmortem · US West - SIP · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hIntermittent connection timeouts in the Frankfurt regionminor resolved · Europe Central - Real Time Communication · official notice ↗ · replay & discuss
- → resolved · lasted 3.7 hObservability upload and Agent Simulations failurescritical postmortem · Cloud Dashboard (cloud.livekit.io) · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hInvestigating delayed cloud agent builds in US Eastminor resolved · US East - Cloud Agents · official notice ↗ · replay & discuss
- → resolved · lasted 47 minInvestigating scaling issue affecting Cloud Agents in EU (Frankfurt)minor resolved · Europe Central - Cloud Agents · official notice ↗ · replay & discuss
- → resolved · lasted 1.1 hMonitoring reports of intermittently increased API latency impacting Egress, Ingress, and SIPminor postmortem · Global Egress, Global Ingress, Global SIP · official notice ↗ · replay & discuss
- → resolved · lasted 1.2 hInvestigating reports of intermittently increased API latency impacting Egress, Ingress, and SIPminor postmortem · Global Egress, Global Ingress, Global SIP · official notice ↗ · replay & discuss
- → resolved · lasted 3 hCloud Dashboard, Analytics Services, and Billing API failuresmajor resolved · Cloud Dashboard (cloud.livekit.io), US West - Analytics Ingestion · official notice ↗ · replay & discuss
- → resolved · lasted Some sessions incorrectly shown as activenone resolved · official notice ↗ · replay & discuss
- → resolved · lasted 1.6 hIdentified increased agent join latencies in eu-centralminor postmortem · Europe Central - Cloud Agents · official notice ↗ · replay & discuss
- → resolved · lasted 20 minInvestigating reports of one-way audio issues in LiveKit Phone Numbersminor resolved · Global SIP · official notice ↗ · replay & discuss
- → resolved · lasted 3.7 hLiveKit dashboard failing to loadmajor resolved · Cloud Dashboard (cloud.livekit.io) · official notice ↗ · replay & discuss
- → resolved · lasted 1.6 hElevated inference errors — US Eastnone resolved · official notice ↗ · replay & discuss
- → resolved · lasted 4.1 hAgent session analytics displaying incorrect values in EU Central and India regionsminor resolved · India - Analytics Ingestion, Europe Central - Analytics Ingestion · official notice ↗ · replay & discuss
Related services
- Degraded / minor incidentTwilioDegraded / minor incident→
- Degraded / minor incidentSendGridDegraded / minor incident→
- OperationalMailgunOperational→
- no official feedPostmarkno official feed→
- no official feedMailchimpno official feed→
- OperationalVonage APIOperational→
- OperationalPlivoOperational→
- OperationalBird (MessageBird)Operational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.