Live  /  TwentyThree  /  Incident

TwentyThree: Slow responses from the TwentyThree platform — Resolved

TwentyThree · twentythree.comResolved2024-02-12 15:00 UTC
Public — what happened

Summary

TwentyThree said that on February 9, 2024, its platform turned away much of its incoming traffic and answered the remaining requests very slowly, with delays of up to 30 seconds, during two windows: 09:39 to 09:49 UTC and 09:59 to 10:01 UTC. During those periods, the video management tools were unavailable or very slow, some hosted webinar Hubs and embedded video players could not be reached, and viewers could not join webinars, although webinars already in progress kept streaming. The company said a third-party tool with a faulty setup sent a huge surge of traffic, roughly what it normally sees over several days, packed into about 10 minutes. It said it added capacity and deployed a fix that restored service by 10:01 UTC, posted its resolution update on February 12, and plans stricter limits on incoming traffic.

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 TwentyThree 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 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

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

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