GlobeLatency Troubleshooting: No Reply, Stuck Tests & More
Most GlobeLatency problems have simple causes: a blocker or firewall stopping requests, a tab in the background, an old cached version of the page, an http address on an https page, or a location lookup that failed. This guide lists symptoms, the likely cause and the exact fix for each.
On this page
- First aid checklist
- Symptom: all destinations say No reply
- Symptom: one or two destinations say No reply
- Symptom: my custom destination never replies
- Symptom: test is slow or seems stuck
- Symptom: results are much higher than my ping
- Symptom: colours or verdict look odd
- Symptom: map problems
- Symptom: alerts do not fire or fire too often
- Symptom: history or settings disappeared
- Symptom: the page behaves differently on mobile
- Still stuck?
- Common mistakes and myths
- What to do next
Quick answer: start with the basics: reload the page (hard refresh), keep the tab in front, turn off ad blockers or VPN for a moment, and check that other websites open. If one specific thing is wrong, find the symptom in the sections below.
First aid checklist
- Hard refresh: Ctrl+F5 on Windows and Linux, Cmd+Shift+R on Mac.
- Open another website to confirm your internet works.
- Try a private or incognito window without extensions.
- Disable VPN, proxy and content blockers for this site.
- Keep the tab visible and the device awake.
- Try a different browser or a different network (for example mobile hotspot).
Symptom: all destinations say No reply
Likely causes: no internet, a firewall or security product blocking cross-site requests, a corporate proxy, a DNS problem, or an extension that blocks "tracking" requests.
Fix: verify connectivity, test in a private window, disable extensions one at a time, and try another network. On a work network, ask IT whether outbound HTTPS to external hosts is restricted. The explanation of what a no-reply means is in how GlobeLatency measures.
Symptom: one or two destinations say No reply
Likely causes: the server is down or rate-limiting, it blocks your country, or your route to it is broken.
Fix: retry after a minute, then compare with other destinations of the same provider. If the rest reply, the issue is with that destination or its route. A report with a few failures is still valid.
Symptom: my custom destination never replies
- Check it uses https://. Mixed content is blocked.
- Open the address directly in a new tab to see whether it loads and whether the certificate is valid.
- Internal hostnames work only if your own device can reach them.
- A firewall on the server may block requests from your IP.
See Destinations and custom hosts.
Symptom: test is slow or seems stuck
Destinations that do not respond wait for the 10 second timeout, and up to three are measured at a time, so a selection with many unreachable hosts takes longer. A background tab also throttles activity. Keep the tab visible, or press Stop and run again with fewer destinations. Remember that a stopped test is not saved.
Symptom: results are much higher than my ping
That is expected to a degree. HTTPS timing includes extra steps. See ping vs HTTPS latency. If it is higher by hundreds of milliseconds, look for a VPN, a busy network or Wi-Fi problems with troubleshoot high latency.
Symptom: colours or verdict look odd
- Green with a big ms number: the destination is far away and you are better than typical for it. See the world comparison.
- Red with a small difference: not possible when the difference is under 30 ms or the value under 50 ms; if you see it, hard refresh to load the latest version.
- No world data: custom destinations and brand-new shared ones use fixed bands.
Symptom: map problems
| Problem | Cause | Fix |
|---|---|---|
| You marker missing or wrong | Location lookup blocked or inaccurate | Allow external requests, disable VPN, reload |
| Pins in odd places | Anycast addresses or failed location lookups | Expected; unlocated hosts appear near you |
| Pins stay grey | Not enough readings yet (needs three) or tab in background | Wait a few cycles, keep the tab visible |
| Map empty | No destinations selected | Select a template in Test mode first |
See the live map guide.
Symptom: alerts do not fire or fire too often
Alerts need to be enabled and the tab must be open. They fire when a destination goes down or exceeds the time threshold, at most once every 30 seconds per destination. Browsers may block sound until you click on the page. Adjust thresholds or per-destination limits. See Alerts and thresholds.
Symptom: history or settings disappeared
They live in your browser local storage. They vanish when site data is cleared, in private windows after closing, or on another device or browser. Server reports remain available through their links. See Privacy and data.
Symptom: the page behaves differently on mobile
Mobile browsers pause background tabs aggressively and the radio changes state to save power, which can add delay to the first request after idle. Keep the screen on and the tab open, and expect mobile networks to vary more than cable. Measure at different times and compare Wi-Fi with mobile data.
Still stuck?
Note your browser and version, whether a VPN or blocker is active, what you selected, and a screenshot or report link. Use the support chat on the page if available and send that information.
Common mistakes and myths
- Assuming No reply means the site is down for everyone. It means it did not reply to you.
- Reading too much into one run. Repeat before concluding.
- Testing through a work VPN and blaming the ISP.
What to do next
Return to Running a test, learn about limits in Accuracy and limitations, or start a new test.
Frequently asked questions
Why do all destinations show No reply?
Usually you are offline, a firewall or content blocker is blocking requests, or a VPN or proxy interferes. Open another website to check your connection, disable blockers for this page, and retry. Corporate networks sometimes block external hosts.
Why does only one destination show No reply?
That server may be down, may block your network or country, or may have changed its address. Retry later and check whether others in the same category reply. A single persistent no reply is usually that destination, not you.
Why is the colour or verdict different from what the guides describe?
You may be seeing an older cached version of the page. Hard refresh with Ctrl+F5 (Cmd+Shift+R on Mac). The site fingerprints its files to avoid this, but proxies or the browser can still hold older copies.
Why is the You marker missing or wrong on the map?
Location comes from your public IP through external services. If those are blocked or you use a VPN or IPv6-only connection, the lookup can fail or be off. The map then falls back to a default position so the marker still appears.
Why did my test stop by itself?
A tab left in the background, a sleeping computer or a lost connection can pause or abort requests. Keep the tab visible and the device awake while a test runs.
Why can I not add an http:// address?
Browsers block insecure http requests from a secure https page. Use an https address for your custom destination.