Ping is the first tool anyone reaches for when the network misbehaves. Here is how to ping an IP address on Windows, Mac and Linux, how to read what comes back, and how we use ping every day at Tronic to diagnose VoIP call-quality problems.
What does ping actually do?
Ping sends a tiny packet (an ICMP echo request) to another device and times how long the reply takes. It answers two questions: can my computer reach that address at all? and how fast and consistent is the path? That makes it perfect for checking whether a server, printer, router or phone system is reachable.
How to ping on Windows
- Press Windows key + R, type
cmdand press Enter (or search for “Command Prompt”). - Type
ping 8.8.8.8and press Enter (that address is Google’s public DNS – a handy always-on target). - You will get four replies. To ping continuously, use
ping -t 8.8.8.8and press Ctrl + C to stop.
You can ping a name instead of an IP address too: ping tronic.com.au. If pinging the IP works but the name fails, your problem is DNS, not connectivity.
How to ping on Mac and Linux
- Open Terminal (on Mac: Applications > Utilities > Terminal).
- Type
ping 8.8.8.8. On Mac/Linux ping runs continuously by default – press Ctrl + C to stop and see the summary.
Reading the results
- time= – the round trip in milliseconds. Under 20 ms is excellent, 20-60 ms is normal for Australian internet, and consistently high or wildly varying times (jitter) cause choppy VoIP calls.
- TTL= – how many network hops the packet had left. Mostly useful for spotting unusual routing changes.
- Request timed out / 100% packet loss – no reply. The device is off, unreachable, or a firewall is dropping pings (many servers deliberately ignore ping, so no reply does not always mean down).
- Packet loss – even 1-2% loss is enough to make phone calls sound robotic. Anything above 0% on a stable link is worth investigating.
Using ping to troubleshoot VoIP and phone system problems
Because VoIP calls are just real-time data, ping is a brilliant first test when call quality drops. A quick sequence we use with customers:
- Ping your router (usually
192.168.0.1or192.168.1.1). Bad times here mean a local network or Wi-Fi problem. - Ping 8.8.8.8. Good times to the router but bad times here point at your internet connection.
- Watch for spikes during calls. Run
ping -tduring a bad call – if times spike when the call breaks up, something on the link is saturating it (large uploads and cloud backups are the usual suspects).
If you are a Tronic customer chasing call-quality issues, check our Tronic Cloud status page first, then our SIP and firewall requirements guide – and for 3CX users, the 3CX app troubleshooting guide. Still stuck? Our remote support team can run these tests with you.
Frequently asked questions
What IP address should I ping to test my internet?
8.8.8.8 (Google DNS) and 1.1.1.1 (Cloudflare DNS) are the standard always-on test targets.
Why does ping work but websites will not load?
If ping 8.8.8.8 succeeds but ping google.com fails, DNS is broken – your device cannot turn names into addresses. Restart your router or set your DNS servers to 8.8.8.8 / 1.1.1.1.
Is high ping bad for phone calls?
Yes. Above roughly 150 ms round trip, callers start talking over each other, and jitter (variation in ping times) causes robotic audio. VoIP wants a low and steady ping.
Ready to see 3CX in action?
Tronic is an Australian 3CX partner. We host, licence, configure and support 3CX powered by Tronic Cloud for businesses across the country, and we can even add a 24/7 AI receptionist on top. Get in touch for a plan enquiry or call us on (03) 9970 5220.

