Two vantage points, every number real: your browser measures its own delay to this store, and the hosting node self-checks every service port. Nothing is simulated or padded.
Your latency
your connectionmeasuring…
Median of 3 sequential probes against the store, refreshed every 30 s — measured live from your browser to the store edge. This is the delay your connection actually experiences.
This session · 0/20 samples
no successful sample yet
Checking monitors…
Origin self-checks run from the hosting node itself and prove each service answers; your real delay is the headline number above, measured by your browser.
Running first probe round…
Real probes, not promises
A background timer probes the store infrastructure and the public demo server every 5 minutes and reports exactly what it observes.
Two vantage points, labeled honestly
The server probes run on the hosting node itself, so their connect times are loopback-fast (~1 ms): they prove the services answer and how responsive they are — shown as “origin self-check”, not as your network delay. The headline “Your latency” is measured by your own browser (median of 3 probes to this store every 30 s) — that is the real delay your connection experiences.
Uptime you can audit
Uptime percentages are computed only from stored checks and appear once at least 10 samples exist — until then the page says history is building. Monitoring started Aug 28, 2026; the baseline (core services and the Minecraft demo's real state) is displayed exactly as measured, never faked green. The website row covers public reachability, so 443 has no separate monitor.