Real-time statuspage notification for the recent us-east media connectivity incident

Telephony
1

Hi LiveKit team,

We rely on LiveKit for production voice traffic and recently hit user-visible audio degradation on a call that we traced back to this incident:

https://status.livekit.io/incidents/2sjw9ph24lb2 — intermittent media-server connectivity in us-east.

Affected room URL: https://cloud.livekit.io/projects/p_3tqm7ro6kbs/sessions/RM_gr4grYfFhHMB

We’re subscribed to statuspage updates, but did not receive any notification while this incident was active. The first we knew of it was after the fact, when we went looking for a root cause for our affected call.

Question: was this incident posted on statuspage in real time (and we missed the notification), or was it added retroactively for documentation purposes?

Thanks — happy to share additional session details privately if useful for correlation on your side.

2

@CWilson - possible to help answer this please?

3

We endeavour to update the status page in real time, though occasionally incidents are posted after the fact for transparency.

Looking at the internal incident channel however, I see this specific status was posted DURING the incident, so I’m not sure why you didn’t get the notification.

4

@darryncampbell - Appreciate your response. The incident mentions the dates of May 12th and 13th too. When was the incident first published?

Maybe it was NOT published on 15th? But we don’t see any alerts for 12th and 13th as well surprisingly :confused:

5

I see the following message on the incident:

Posted 6 days ago. May 15, 2026 - 09:57 PDT

Which tracks with internal conversations.

The incident is still awaiting a proper RCA / post-mortem. Rather than speculate myself why the incident refers to those earlier dates, I would expect the root cause analysis to contain that info, and the incident should be updated in the next few days.

6

Thanks for the response darryn, it was weird that we didn’t receive a slack alert and hence I reached out. Thanks for clarifying this.

I am now thinking if there was a failure while delivering a message to slack

7

I am now thinking if there was a failure while delivering a message to slack

I’ll notify the support team about this thread, to be aware of the possibility and look out for similar reports.

8

Thanks @darryncampbell - please let us know if others have also reported this issue