Realtime Ping Dashboard

Multiple nodes continuously Ping / TCPing a target, plotting live latency curves and packet loss per location — a screenshot-friendly big-screen view

Probe Configuration

Select nodesSelected 0 / 10

Loading nodes…

With no nodes selected, one available node is used automatically

Live latency (ms)

Latency curves per node will be drawn here after you start

Node latency / loss

No data yet

What is the Realtime Ping Dashboard for

The realtime ping dashboard has real nodes spread across locations continuously Ping or TCPing the same target, plotting each round's latency (RTT) as a live line — one line per node, color-coded by network group (China Telecom / Unicom / Mobile and overseas). Unlike a one-shot multi-location ping, it lets you watch latency jitter and intermittent packet loss over time, ideal for debugging flaky connectivity.

The layout is screenshot-friendly: a multi-node live latency chart on the left and a per-node latency / packet-loss board on the right. Pause to freeze the frame, resume to continue sampling, or export a CSV snapshot. If the target blocks ICMP, switch to TCPing to gauge latency from a specific port's connectivity.

FAQ

How does this differ from a normal multi-location ping?

A normal multi-location ping measures once and returns a result; the realtime dashboard keeps sampling over many rounds and plots live lines, revealing jitter and intermittent loss over time — better for long observation and sharing screenshots.

Why does it stop automatically?

To avoid tying up probe resources indefinitely, each session has a duration and round cap; once reached it auto-recycles and stops sampling. Collected data stays on the chart and can be exported.

What if the target does not respond to ping?

Many servers block ICMP. Switch to TCPing and specify a port (e.g. 443) to gauge latency from application-layer connectivity.

How many nodes can I watch at once?

Up to 10 nodes per session, to avoid fanning out to too many nodes at once. With no nodes selected, one available node is used automatically.