How to test your internet connection with a simple ping
When a web page refuses to load, the cause may be somewhere between your device and the destination server. Your home connection could be offline, a Wi-Fi signal may be weak, or a network route may be temporarily unavailable. The website itself might also be busy, filtered, incorrectly configured, or affected by a hosting problem.
A ping test is a quick way to check whether your device can reach another computer across the internet. It sends small data packets to a chosen address and measures whether they return, how long the trip takes, and whether any packets disappear. This makes ping useful for basic network troubleshooting, although it cannot diagnose every web problem.
The test is especially handy on Australian connections where a fault may involve home Wi-Fi, the NBN link, a mobile network, or a long route to an overseas server. It takes only a few seconds, costs nothing, and can give you clearer evidence than repeatedly refreshing a blank browser tab.
What a ping test actually checks
Ping uses the Internet Control Message Protocol, usually shortened to ICMP. Your device sends an echo request to an IP address or domain name, and the destination may send back an echo reply. The result normally shows the round-trip time in milliseconds, along with the number of packets sent and received.
A reply confirms that a path exists between your device and the target, but it does not prove that a website is working correctly. A server can respond to ping while its web application is down, and some networks deliberately ignore ICMP requests for security or traffic-management reasons. A failed ping therefore needs interpretation rather than an immediate assumption that your internet is disconnected.
You can test several points to locate the likely trouble. Pinging your local router checks the connection between your device and the home network. Pinging a public address such as 1.1.1.1 checks broader internet access without relying on domain-name lookup. Pinging a website name tests both connectivity and, usually, DNS resolution.
Running the command on your device
On Windows, open the Start menu, type Command Prompt, and launch it. Enter ping 1.1.1.1 and press Enter. Windows normally sends four packets and displays the response time for each one. To test a website name, use a command such as ping example.com; replace the example with the domain you need to investigate.
On macOS, open Terminal from Applications or Spotlight and run the same command. macOS and Linux systems generally continue sending packets until you stop them with Control-C, after which a summary appears. You can limit the test with ping -c 4 1.1.1.1, which requests four replies and then ends automatically.
Start with your router’s address if you know it. Common private addresses include 192.168.0.1 and 192.168.1.1, though the exact address varies between routers and internet providers. You can find the default gateway in your device’s network settings. If the router responds quickly but a public address does not, the fault may sit between your home network and the wider internet.
Understanding latency and packet loss
Latency is the time needed for a packet to travel to the target and return. A result such as time=18ms is generally responsive for ordinary browsing, while much higher figures may produce delays in online gaming, video calls, and remote work. The right benchmark depends on the target’s location: a server in Sydney will usually answer faster from Canberra than a server hosted in North America.
Packet loss appears when some requests receive no reply. A small amount may be caused by temporary congestion or a server’s policy, but repeated loss at several targets suggests a connection problem. If every ping times out, check whether the device is connected to Wi-Fi, whether the router has internet access, and whether a firewall is blocking ICMP traffic.
Compare results rather than relying on one test. If the router has zero loss, 1.1.1.1 has occasional loss, and a particular website fails completely, the issue may be with the route or that website. If the router itself is unreliable, move closer to the access point, test with an Ethernet cable, or restart the networking equipment according to the provider’s instructions.
A mobile hotspot can provide another useful comparison. For example, someone in regional Queensland may find that a home NBN connection fails while a Telstra or Optus mobile connection reaches the same address. That comparison does not repair the NBN service, but it helps separate a local Wi-Fi issue from a broader site or routing problem.
When ping works but the page does not
A successful ping does not guarantee that a browser can retrieve a page. Browsing also depends on DNS, TCP or HTTPS connections, certificates, server software, and the website’s own application. A destination may permit ping while refusing web traffic on ports 80 or 443, or it may return an error because its hosting platform is overloaded.
A 503 Service Unavailable message usually points to a temporary problem at the server or an upstream service rather than a fault in your laptop. You can read a clear explanation of what a 503 error means before deciding whether repeated local troubleshooting is worthwhile. Waiting briefly and trying again may be more effective than changing network settings.
DNS problems can create a different pattern. Pinging an IP address may work while pinging the domain name reports that the host cannot be found. In that case, check the configured DNS servers, restart the router, or try a recognised public DNS service if you understand the change. A browser cache can also preserve old loading information; these steps explain how to clear browser cache safely.
Filtering is another possibility. Schools, workplaces, public libraries, and some managed networks may block particular domains while general internet access remains available. A café in Melbourne, a hotel in Cairns, and a home network in Adelaide can all apply different restrictions. Testing from another legitimate network can reveal whether the failure is tied to one connection.
Practical checks before escalating a fault
Use the following sequence to keep the investigation simple:
- Check that Wi-Fi or mobile data is enabled and confirm that other websites load.
- Ping the router, then a reliable public IP address, and finally the affected domain.
- Compare Wi-Fi with an Ethernet connection or a separate mobile hotspot.
- Record packet loss, response times, the exact error message, and the time of testing.
- If the problem continues, check your NBN or mobile provider’s outage information before contacting support.
Keep the target consistent when comparing results. A ping to a nearby Australian server may be fast while an international destination naturally takes longer, so comparing Sydney with Singapore or the United States can give a misleading impression. Run the same command several times and note whether performance changes during peak evening usage or local events.
Restarting a router can clear a temporary session or address problem, but it will not fix a damaged cable, an outage, or a failed website. Avoid changing several settings at once because you may lose track of what helped. On shared networks, ask the network administrator before altering DNS, firewall, or proxy settings.
If a page still fails after the basic checks, save the evidence. A screenshot of the browser error, the ping summary, the tested domain, and your connection type gives an internet provider or site administrator useful information. Mention whether you were using NBN, mobile broadband, workplace Wi-Fi, or public access, since each network can follow a different route.
A simple ping is best viewed as a first diagnostic signal. It can show whether packets travel successfully and how consistently they return, but it cannot confirm that a web server, database, login system, or content-delivery service is healthy. Combine it with browser checks, another network, and the exact error message to form a more reliable picture.
Run the three-point comparison—router, public IP, and affected domain—when the next loading problem appears. Keep the results for reference, retry the page after a short interval, and use the evidence to decide whether the issue belongs to your device, your connection, or the website itself.