Service Downtime & The 5-Minute Rule

Errors & Fixes Reviewed September 6, 2026 1 min read

Most connection drops that get reported as outages are not outages at all — they are automated systems doing exactly what they are supposed to do, and finishing on their own well within the time it takes to write a ticket about them.

Why it happens

A brief connection gap has two ordinary, self-resolving causes far more often than it has an actual node failure: automated DDoS mitigation reacting to a traffic spike and clearing itself once the spike passes, or a scheduled restart completing its normal startup sequence. Both look identical to a player as a dropped connection, and both are typically over well inside five minutes with no action needed from anyone.

What five minutes actually buys

If you waitIf you do not
Mitigation or a scheduled restart finishes on its own, connection returnsA ticket opens for something already resolving itself
Monitoring has already flagged a genuine outage on the status page, if there is oneSupport spends a cycle confirming what monitoring already confirmed
Check the status channel first — it is often already answered

Verified infrastructure problems get posted there as soon as monitoring confirms them, which is usually faster than a ticket would be answered anyway.