How to check your network latency on a Mac

The quick answer

Open Terminal and ping a reliable host 20 times:

ping -c 20 1.1.1.1

--- 1.1.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 15.4/18.9/42.0/5.8 ms

Read the last two lines:

• avg is your typical latency.
• stddev is a good stand-in for jitter: how much latency jumps around. Small is good.
• packet loss should be 0%. Even 1–2% makes calls choppy.
• max far above avg means spikes, the kind that freeze a video frame.

Is it your Wi-Fi or your provider?

Ping your router, then the internet, and compare. Find the router address first:

route -n get default | grep gateway
ping -c 20 192.168.0.1   # use the gateway address from above

Router ping	Internet ping	Problem is
Low and steady (1–5 ms)	High or lossy	Your ISP or beyond
High or lossy	High or lossy	Your Wi-Fi or local network
Low	Low	Probably the service you’re using

On Wi-Fi, a router ping above 10 ms or with spikes into the hundreds points at signal or interference. Hold Option and click the Wi-Fi icon in the menu bar to see RSSI, noise, channel and transmit rate. An RSSI weaker than about −70 dBm is where things get unreliable.

Latency under load: networkQuality

Plain ping measures an idle connection. Most real lag happens when something else is uploading or downloading at the same time, which is called bufferbloat. macOS ships Apple’s own test for it:

networkQuality

==== SUMMARY ====
Uplink capacity: 47.133 Mbps
Downlink capacity: 63.303 Mbps
Responsiveness: Low (1.070 seconds | 56 RPM)
Idle Latency: 20.144 milliseconds | 2978 RPM

Compare Idle Latency with Responsiveness. In this example the line is 20 ms when quiet but over a second when busy: a video call will fall apart the moment a backup starts. That’s a router or ISP queueing issue. Turning on SQM or “Smart Queue” on your router, if it has one, is the usual fix.

Useful flags: -v for detail, -s to test download and upload one after the other, and -I en0 to test one interface.

Find where along the route it goes wrong

traceroute shows each hop between you and a host, with the time to each:

traceroute -n 1.1.1.1

A jump that stays high for every hop after it marks where the delay starts. A single slow hop followed by fast ones is just a router that answers traceroute slowly; ignore it.

Keep a record

Latency problems are often intermittent: fine when you test, bad at 8 pm. A one-liner can log a ping every 10 seconds with timestamps:

ping -i 10 1.1.1.1 | while read l; do echo "$(date '+%F %T') $l"; done >> ~/latency.log

It runs until you press Ctrl-C, and the log is plain text you can send to your provider.

Seeing it live

Stat Space has an opt-in latency monitor (Settings › History & backup): one ICMP echo every 10 seconds to 1.1.1.1 or a host you choose, from an unprivileged socket rather than a spawned ping. Latency, loss and jitter are charted and kept in its 30-day history, so you can scroll back to last Tuesday evening. A VPN chip appears when a tunnel carries your traffic, since that changes every number. The Network tab also has on-demand ping with a latency chart, traceroute, DNS lookup and a speed test that runs Apple’s networkQuality. All free.