Latency Test
Measure round-trip time from your browser to the access points that matter. Compare brokers, cloud regions or any HTTPS target, and keep an honest record of how each number was obtained.
Cloud Ping checks latency to public cloud regions without signing in. Broker Ping remains protected and requires sign-in.
Sign in to run a test
Measurements are attributed to the person who submitted them, so running a test needs an identity.
Or use the shared access password:
No sign-in method is configured yet. An administrator needs to set up GitHub or LinkedIn sign-in, or set a shared client password in the admin console.
Locating you…
Loading targets…
Where your targets are
Marker colour is the median round trip from your browser. Positions are published by the provider where one is known, and otherwise estimated from the address — hover a marker to see which, because an estimate and a published location are not the same claim.
Results
Rows are grouped by measurement method. A tcp_connect of 12 ms and an
https_fetch_approx of 12 ms are not the same quantity, so they are never
ranked against each other.
| Server | Method | Platform | Median | P95 | Best | Jitter | Samples |
|---|
What each method actually measures
https_ttfb- Browser. From request sent to first response byte. Needs the target to send
Timing-Allow-Origin; without it no value is recorded. https_fetch_approx- Browser. Wall clock around a
no-corsfetch — DNS, TCP, TLS, HTTP, error handling and browser scheduling all included. Useful for comparing targets within one run; not an absolute round-trip time. ws_echo- Browser. Opens one WebSocket to this service and times ~20 application-level echoes over the established connection. Because the handshake is paid once, this is the only browser method that can report jitter.
tcp_connect- Probe agent. SYN to SYN-ACK. This is the only honest measurement of MT4/MT5 access points, which speak a proprietary binary protocol on :443 and are not HTTPS servers at all — a browser can neither time them nor open a raw socket.
icmp_ping- Probe agent. ICMP echo round trip. Widely rate-limited or dropped; absence of a reply is not evidence that a host is down.
Frequently asked questions
- Can I measure latency to cloud providers?
- Yes — use Cloud Ping to measure HTTPS latency to Google Cloud, AWS, Alibaba, Oracle, Huawei and others. It does not need an account.
- Why are there different measurement methods?
- Because a number without its method is noise. A browser
https_fetch_approxincludes DNS, TCP, TLS and the browser's own scheduling, while an agenttcp_connectis only the SYN → SYN-ACK time. We never rank results from different methods against each other. - Why do some targets not return a timing?
https_ttfbneeds the target to send aTiming-Allow-Originheader. MT4/MT5 access points are not HTTPS servers at all, so they can only be measured by an approved probe agent.