Live / TwentyThree / Incident
TwentyThree: Webinar Service Disruption — Resolved
TwentyThree · twentythree.comResolved2025-09-10 08:40 UTC
Public — what happened
Summary
TwentyThree reported a disruption to its webinar service that began on 2025-09-03 at 08:00 UTC, during which large parts of the platform stalled and webinar streams restarted. The company said the trigger was its newly launched action cards feature in the webinar room, where an incorrectly set cache header generated far too many requests to one of its services and overloaded it. TwentyThree said it corrected the cache header setting and marked the incident resolved on 2025-09-10 at 08:40 UTC.
Timeline
- Started — 2025-09-03 08:00 UTC
- Resolved — 2025-09-10 08:40 UTC · 7 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach TwentyThree against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for TwentyThree: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the TwentyThree report →
More from TwentyThree