Azure Speed Test

PsPing Network Latency Test for Azure

Generate a ready-to-run PsPing command and compare network latency to Azure regions from your own connection.

Build your PsPing command

Select an Azure region and sample size. The generated command tests TCP port 443.

Windows command line
Region
West US
California
Public test endpoint
s8westus.blob.core.windows.net:443

Generated command

psping.exe -n 20 -w 5 s8westus.blob.core.windows.net:443

What this command measures

This is TCP connection latency to a public Azure Storage frontend. It does not identify an exact physical facility, measure application response time, or represent VM-to-VM payload latency.

Download PsTools Test the same region in your browser

PsPing supports Windows 8.1 or later and Windows Server 2012 or later. The first run may ask you to accept the Microsoft Sysinternals license.

Run the PsPing latency test

  1. Step 1:

    Download and extract PsTools

    Extract the complete ZIP archive to a local folder. PsPing depends on files distributed with the PsTools package.

  2. Step 2:

    Open Command Prompt in that folder

    In File Explorer, open the extracted folder, select the address bar, enter cmd, and press Enter.

  3. Step 3:

    Paste the generated command

    Run the command generated above. The -n option controls measured samples and -w controls warm-up samples.

  4. Step 4:

    Review the connection statistics

    Compare the average and range across multiple runs. Do not select an Azure region from a single minimum result.

Example PsPing output

Command Prompt showing PsPing TCP connection statistics for the West US Azure Storage endpoint with 20 packets sent, 20 received, zero loss, and minimum, maximum, and average latency
Real PsPing TCP connect output for the West US test endpoint. This screenshot adds -q to hide individual connection attempts. Your latency values will vary by network, location, and time.

Minimum

The fastest successful TCP connection observed.

Average

The most useful single value for comparing runs.

Maximum

The slowest connection and a clue to instability.

Failures

Timeouts can indicate DNS, port, or firewall issues.

Browser test vs PsPing

Both are useful, but they observe different parts of the connection. Their numbers should not be expected to match.

Measurement

Browser test
Browser-observed HTTPS request duration. Connection reuse means DNS and TLS are not included in every sample.
PsPing
TCP connection establishment time to one host and port, or ICMP round-trip time when the target supports ICMP.

Best for

Browser test
Comparing the experience of reaching the public Azure Storage endpoints used by this site.
PsPing
Repeatable command-line diagnostics, TCP port checks, and controlled host-to-host testing.

Limitations

Browser test
Affected by browser scheduling, protocol behavior, connection reuse, and the public service endpoint.
PsPing
A TCP connect test does not measure application response time or VM-to-VM payload latency.

Requirements

Browser test
A modern browser. No download or installation is required.
PsPing
Windows 8.1 or later, or Windows Server 2012 or later, plus PsTools.

Frequently asked questions

Where can I find all PsPing parameters?
Visit the official Microsoft PsPing documentation for ICMP, TCP connect, latency, and bandwidth syntax.
Why might ICMP ping fail against an Azure target?
Many Azure managed-service endpoints do not answer ICMP. Azure VMs may also block it in the network security group or operating-system firewall. A failed ICMP ping does not prove that the service is unavailable; test a known open TCP port such as 443 instead.
Does this measure an exact Azure datacenter location?
No. Azure region locations on this site are region-level metadata, not physical facility addresses. The generated command measures the public path to an Azure Storage frontend associated with the selected region.
How should I compare latency between Azure regions?
Use the same PsPing sample and warm-up counts for each target and repeat the test at different times. For Microsoft's published Azure backbone measurements, see Azure Region to Region Latency . Those values are not measurements from your device.