Live  /  TwentyThree  /  Incident

TwentyThree: Slow responses from the TwentyThree platform — Monitoring

TwentyThree · twentythree.comResolved2024-02-09 10:30 UTC
Public — what happened

Summary

TwentyThree reported that its platform was responding slowly, with the problem beginning on February 9, 2024 at 09:52 UTC. The company did not say which customers were affected or what caused the slowdown. It marked the incident as resolved at 10:30 UTC the same day and said further details would be shared later in a post-mortem.

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.