This site runs without ads on purpose — donate to keep it alive →
← all servers
Gathering data

87-gn06.dfw.lagless.gg is still gathering data

We haven't watched this server long enough to know what this time of week normally looks like here — give it a couple of weeks and there'll be a read.

11 / 100 players online right now

Recent (3h)
14
Usual (now)
—
vs. usual
—
Deviation
—
4-wk avg
15.4
Uptime (4 wk)
100%
no outages
All-time peak
25
3 hours ago
Version
Paper 26.3

Players — last 30 days

Download last 30 days: CSV · JSON · one row per ping, ours to measure and yours to check — what the columns mean

What kind of server is this?

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 →

Ups and downs

No slumps in the few hours we've been recording verdicts.

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.

What's changed

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.

Is this your server? Click here to claim it and add a description.

“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.