After the recent storms we have received here on the Sunshine Coast, a lot of delicate technologies take a hit. I myself received an increase in latency spikes on most of my online applications and a decrease in my internet speed. In most cases this can be due to an internal problem in your network but if you perform a few simple steps you can save yourself hours troubleshooting your set up.
In most cases slow internet can be due to peak bandwidth usage or corrupt network infrastructure so the first thing we want to do is try to eliminate some of these variables. First lets open up a Command Prompt window and send some packets to our gateway to ensure there isn’t an issue there.
Windows Key + R: will open your run window. Next type cmd and click ok
This will bring up a command prompt window where we can type some commands to test our latency or PING (Packet INternet Groper) to the desired destination. Next we want to PING our gateway, to find out what your gateway’s IP address is type the following command: ipconfig and press Enter to run the command.
As you can see the IP Address to your gateway will be listed after the Default Gateway indicator. The IP Address for my gateway is 192.168.1.1 your gateway IP will be something different more than likely. Take note of this IP Address as we will send some packets (PING) to this address to test the latency. Next type the command ping 192.168.1.1 this will send four packets to the gateway.
The response time from my gateway is an average of 4ms (milliseconds) which is normal, if the response time is higher then 15ms to your gateway then there may be an issue with your internal network. If your PING test has come back normal then we can test the response time to an external address.
Lets PING an address externally, for this example we will use Google as our destination address. Enter the command ping google.com.au
The average response time for me from Google is 37ms which is normal again, if the response time is higher then 150ms there could be an issue with your Internet Service Provider (ISP). Lets monitor the packets as they travel to the Google server to find out if there is a issue with one of the routes. Type the command tracert google.com.au
The first number at the start of each line is the hop count, how many times the packet has be routed to reach its destination. In most cases your trace route should look like mine and should reflect similar response times as our ping test to Google. Although when i had latency issues on my connection the 2nd route response time was in the 200-400ms range, as you can see this is the route to my local exchange by iinet. If the response time to your local exchange (the 2nd route) is higher than 150ms then there could be an issue with your ISP.
This problem has a higher chance to occur after heavy rain, moisture can effect the telephone lines to your exchange and cause slow internet and high latency. After completing the above steps and the latency to your local exchange is high then you will need to contact your ISP and let them know the results of your PING tests. They will usually ask you to perform some standard troubleshooting tasks to ensure there isn’t any internal network issues. This can save hours on the phone to your ISP or ‘Your Local Tech Guy’ and can usually be a quick fix by your ISP.
I hope this guide helped you solve your slow internet and high latency issues. If this guide did help you please click the like button and share this article with your friends on Facebook. If you have any further questions please leave a comment below and we will answer it as soon as we can.
Thank you for viewing and subscribing to our Blog it helps our community grow.