Saved Latency Reports: Share Links, History & Privacy
Every completed Test is saved to the server and given a link such as /results.php?session=… that anyone holding the link can open. The report shows the same numbers as your screen. Stopped tests and custom destinations are never saved, the page is hidden from search engines, and your recent tests are also listed in your own browser.
On this page
Quick answer: when a test finishes, GlobeLatency saves it and shows a link like /results.php?session=1a2b3c…. Copy and send it, and the recipient sees your full report, including averages, best and worst values, the world comparison and the verdict. Nothing needs to be installed and nobody needs an account.
When is a report saved?
A report is created when a Test completes. Three situations do not produce a report:
- You pressed Stop before the run finished. A partial run is discarded.
- Nothing could be measured at all, for example because you were offline.
- The destinations were all custom ones. Custom destinations are never stored.
If a mixed selection of shared and custom destinations is tested, the report contains only the shared destinations. Your screen still shows the custom ones.
The share link
The link includes a session value of 24 hexadecimal characters. That is 16 to the power of 24 possibilities, so nobody can find your report by guessing or counting up from another one. Anyone who has the complete link can read it; anyone who does not, cannot. Treat it like an unlisted video link: private by obscurity, not by password.
The report page asks search engines not to index it. This prevents your IP-linked results from appearing in public search results.
What a report contains
- The headline verdict and the summary cards (your average, best, worst, reached, difference from the world average, unstable count).
- One tile per destination with your average, best and worst, and the world average, low and high.
- Flags (Down, Slow, Unstable) and colours calculated the same way as on the live screen. See Reading your results.
- Two buttons: Run the same test again and Watch live on the map.
The world comparison on a saved report uses the world statistics available when the page is viewed, so very old reports can show slightly different percentages as the global average evolves. Your own measured values never change.
Run the same test again
This button opens the app with the same destinations selected, so you can compare before and after a change (router restart, cable instead of Wi-Fi, a different VPN server). Because the selection is identical, differences in the new result reflect your network and not your choices.
Watch live on the map
This button opens the live map with the same destinations selected. Use it when a report shows a problem and you want to see whether it is constant or intermittent. See the live map guide.
History in your browser
Separate from server reports, the tool keeps a list of your recent tests in your browser so you can reopen them. It lives in local storage on that browser and device only. It is not synced, not sent to the server, and disappears if you clear site data. Use the share link, not the history, when you need to show a result to someone else.
Practical ways to use a report
- Support tickets: attach the link when you contact your ISP. A report with 10 passes to many destinations is far more useful than "it is slow". See talking to your ISP.
- Before and after comparisons: save one report before a change and another after.
- Remote help: ask a family member or colleague to run a test and send the link so you can see their numbers.
- Team checks: have people in different offices run the same template and compare reports.
Worked example
You work from home and video calls stutter in the evening. At 10:00 you run a 10-pass test (average 46 ms, verdict Good) and save the link. At 20:30 you run the same test: average 98 ms, six destinations Unstable, verdict A little slower than usual. Sending both links to your ISP shows a time-of-day pattern: congestion on the access network in the evening. The links hold the evidence.
Common mistakes and myths
- Sharing a link you want to keep private. Anyone with it can read it.
- Expecting stopped tests to be saved. Let a run finish.
- Expecting custom hosts in the report. They stay local.
- Expecting history on another device. History is per browser.
What to do next
Learn what is stored and why in Privacy and data, or run a test to create your first report.
Frequently asked questions
How do I share my latency results?
Finish a test, then copy the report link shown below the results and send it. Anyone with the link can open the same report without installing anything. The link contains a long random session code, so it cannot be guessed from another link.
Is my report public on Google?
No. Report pages carry a noindex instruction so search engines are asked not to list them. Anyone who has the exact link can still open it, so share it only with people you want to see it.
How long are reports kept?
Reports are stored on the server so the link keeps working. The site owner can apply a retention policy, so do not rely on a link as permanent archival storage. Take a screenshot if you need a permanent record.
Why is my custom destination missing from the report?
Custom destinations exist only in your browser. They are shown on screen during the test but never sent to or stored on the server, so they are not part of the saved report.
Where is my test history stored?
In your browser local storage on this device. It lists your recent tests so you can reopen them. Clearing site data, using another browser or another device will not show the same history.
Can I delete a report?
Reports are anonymous and have no account, so there is no personal delete button. If you need a report removed, contact the site owner with the link.