One click runs a safe, bounded HTTPS test against the diagnostic
server over two paths and compares them:
Public edge — straight over the internet (speed.zulucloud.com).
Internal (VPN / on-net) — through the corporate network / VPN
(speed-internal.zulucloud.com). Skipped automatically
if you are not on that network.
Each path measures time-to-first-byte, a bounded download,
and a bounded upload of synthetic random data. Nothing from this computer is
inspected or transmitted except the measurements themselves. The browser test
cannot measure ICMP latency, trace the route, test MTU, or run iperf —
the PowerShell client below is the authoritative detailed test.
Approximate traffic: up to 50 MB down + 16 MB up
(25 + 8 per path).
Running…
Results — Public vs Internal
Summary
Comparison code: —
give this code to support, or use it when you run the detailed PowerShell
test, so the runs can be paired.
Run the detailed test (recommended)
The browser test above is a quick check. For the authoritative
diagnosis — per-hop latency, route trace, MTU, and adapter details — run the
Windows PowerShell client. No install and no administrator rights needed.
Open Windows PowerShell, then run in the unzipped folder:
powershell -ExecutionPolicy Bypass -File .\Invoke-ZuluNetPathTest.ps1 -Mode Standard
When it asks, approve the data volume. Give support your comparison code
above so the detailed run is paired with this browser test.
Results and artifacts (measurements and text route traces
only — never packet captures or any clinical data) are stored on the diagnostic
server for support to review.