What the Ping Latency and Player Count Graphs on PingTrack Show

PingTrack's two history graphs plot a Minecraft server's ping latency and online player count over a selectable time window, so you can see whether lag or population changes are steady, spiky, or tied to particular times. They are most useful for comparing a server against itself over time — not for judging whether a server is "good," since PingTrack publishes no thresholds for either metric.

What each graph plots

Both graphs share the same time axis, which is set by the dashboard's range selector (10 minutes, 1 hour, 24 hours, 7 days, or 30 days). The dashboard also shows a "Last updated" timestamp, so you can tell how fresh the plotted data is before drawing conclusions.

Reading the summary numbers alongside the graphs

The dashboard surfaces several aggregates that pair with the graphs:

• Best Ping in Range — the lowest latency recorded in the selected window.
• Avg / Worst Ping — the typical and highest latency in the window.
• Range Peak and All-Time Peak — the highest player count within the selected range versus the highest ever recorded.
• Range Avg Ping — average latency for the selected range.

A wide gap between Best and Worst Ping, or between Range Peak and All-Time Peak, tells you the server's behavior is variable rather than flat. The graphs show when those extremes happened; the numbers tell you how large they were.

Switching between linear and logarithmic scales

The graph controls include Linear and Logarithmic options. Use linear when values sit in a narrow band and you want to compare ordinary differences honestly. Switch to logarithmic when one or two spikes dwarf everything else — a log scale compresses large values so smaller day-to-day variation stays visible instead of being flattened against the axis. The trade-off is that equal visual steps no longer mean equal millisecond or player differences, so read the axis labels before quoting a value.

Copying graph data

Each graph has a Copy Graph control (shown with a copy icon and a "Graph copied!" confirmation). This lets you take the plotted series out of the dashboard for your own notes, a spreadsheet, or a comparison between two servers. Copy first, then analyze — the dashboard itself does not offer export formats beyond this.

Refreshing and pausing the dashboard

The top bar has a refresh control and a pause toggle next to the time-range selector. Pausing freezes the current view so the numbers and graphs stop updating while you read or copy them; refreshing pulls the latest data. If a graph looks static, check whether pause is engaged before assuming the server has gone quiet.

A practical example

Suppose you want to know whether a server lags during its busiest hours. Set the range to 24 hours, note the Range Peak player count, then look at where the player-count curve reaches that peak. Compare the same x-position on the ping graph: if latency also climbs there, the two are correlated in that window. Switch to logarithmic only if a single outage spike is hiding the rest of the curve. Copy both graphs if you want to keep the comparison.

Limits to keep in mind

PingTrack is a public statistics dashboard; it reports what it has measured and does not state how often samples are taken or guarantee coverage for every server. Treat the graphs as a monitoring aid for spotting patterns and outliers, and confirm anything critical — such as an outage window — against the server's own status information.