Running about 251× its usual level for this time of week, and it's stayed there for over a day now. That's the shape a big update, a viral moment, or a launch event tends to leave.
2105 / 50000 players online right now
Download all time: CSV · JSON · one row per ping, ours to measure and yours to check — what the columns mean
Suggested by visitors. A category appears on the server once 2 people agree — or sooner if the owner says so.
Sign in to suggest a category →8 slumps in the 15 days we've been recording verdicts — the most recent 4 days ago.
Showing the 10 most recent of 48 in the window. Recorded as they happened, so this only reaches back as far as we've been watching this server. A crossing is written down once it clears the threshold decisively — a server sitting right on the line doesn't fill this list, which is why a move can show in the verdict above before it appears here.
Reported by the server itself when we ping it. A change here often explains a bump or slump around the same time — but it's a coincidence in timing, not a measured cause.
“Recent (3h)” is the average player count over the last 3 hours — the window the verdict compares. “Usual” is the average for this weekday and time of day over the past 4 weeks. Deviation is how many standard deviations Recent sits from Usual. “4-wk avg” is the average concurrent player count over the past 4 weeks, counting only moments when at least one player was online. “Uptime” is the share of our own pings that got an answer over those 4 weeks, so it measures reachability from one place rather than whether the server was up for everyone — and a stretch where we weren’t polling leaves no trace in it either way. An outage means two or more failed pings in a row; a single miss is usually a dropped packet, not a server going down. This is a signal, not a diagnosis — dig deeper before drawing conclusions.