The same targets, measured from everywhere at once.
GeoPulse checks a fixed list of services from probes scattered around the world, every minute, and lines up what each one saw. Every check — DNS resolution, TCP connect, TLS handshake, HTTP response — is timed from each country separately. Pick a service from the list to see it country by country.
Widest spread right now
The same check, fastest reporting country against slowest. A big gap here is worth a look before anything else on this page.
Same service, every vantage point
Latency over time
Distribution
The whole shape, not one summary number. Two probes can share a median and have completely different tails — this is what the fourteen-bucket histogram was stored for.
- One row per probe. Every measurement that probe took in this range falls into one of fourteen buckets, chosen by how long it took.
- The numbers across the top are the bucket edges — milliseconds up to 50, then seconds:
.1sis 100 ms,1sis 1000 ms. The spacing is logarithmic, so each step right is a much slower answer than the last.∞holds anything over 10 seconds; its real value is not kept. - Bar height is scaled inside its own row. The tallest bucket in a row is always full height, so bars compare buckets within one probe — never one probe against another. The shape is what to read: a single solid block is a steady connection, two separated humps mean two different paths or two different servers answering.
- p95 on the right — 95% of measurements came back at or under this. It is derived from the summed histogram across the whole range, which is why it stays correct at 7d and 30d. Percentiles cannot be averaged; the counts they come from can be added.
- p95 is interpolated inside the bucket it lands in, so read it as a magnitude, not an exact figure.
- This panel is built from hourly rollups, so it stays empty on the 1h range.