Live  /  mux  /  Incident

mux: Elevated webhook delivery latency

mux · mux.comMinor incidentResolved2026-09-24 18:21 UTC
Public — what happened

Summary

Mux reported a minor incident in which webhook notifications reached customers later than normal on September 24, 2026. The company said that from 16:40 UTC to 17:36 UTC, events typically arrived about 5 minutes late, and some took as long as 15 minutes, though none were lost and all were eventually sent. Mux said video processing, playback and API requests kept working normally. It attributed the delays to a problem in one of its internal database clusters, said that problem had been fixed with delivery steady since 17:36 UTC, and marked the incident resolved at 18:21.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach mux against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for mux: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the mux report →

More from mux

Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.

The full archive is on the mux status & history page.

Related: mux status & history. SquidGrid is not affiliated with mux.