Question Sudden dip in speed and high latency ?

[Kaitto]

Hello, let me preface this by saying that my internet is by far no means anything great. It sometimes (at least once a week) gets wonky late at night and I face a few disconnections, it's Toshima Cable Network but lately it's been really bad. Ever since it went offline yesterday it came back with horrid speeds and extreme latency to the point even images take a while to load. The problem is, it only happened to my PC, my wi-fi is fine; I didn't mess with the cable so I doubt it's that, the speed is the same with or without VPN so probably not throttling. I checked my resource manager to see if there was anything suspicious hogging all the bandwidth and nothing showed up so I'm running out of ideas here. My usual speed os 100mbs on ethernet and right now I'm getting 2mbs.

Any help would be appreciated, thank you.

 

[bill001g]

Are you sure the latency is really higher. Do you have old test data for ping to say 8.8.8.8.

This sounds like a issue with the ISP. Since they are going to ask you to do it anyway when you call make sure you power cycle the modem and the router.

Pretty standard tests. Ping your router IP to be sure you see no packet loss or high latency. This pretty much tests that you pc is ok and likely the router software and hardware.

Then ping a IP like 8.8.8.8 with a problem as bad as you report you should see packet loss or high latency even with a ping command.

What you might also do just to avoid a stupid ISP blaming google for the problem is run tracert 8.8.8.8. It is not likely going to show you the real problem because it does not run long enough. The main goal is to get the IP of routers in the path. You now want to test ping to the IP in hop 2. This is the ISP first router. Hopefully they have not rig it to not respond to ping.

The goal here is to show the ISP that ping is good to your router IP so everything is fine with your equipment but you see issue when you ping the ISP router.

 

[MJS WARLORD]

Check the following.

right click the icon to the internet to the left of your speaker icon , click on change adapter options , right click your internet connection icon and choose properties , click on internet protocol v 4 to highlight it then properties , on the bottom half of the page you are looking at now , click on the button use the following dns , now in the first box you need 8 8 8 8 and in the second you need 8 8 4 4 , finally tick validate settings before exit .

 

[Kaitto]

Are you sure the latency is really higher. Do you have old test data for ping to say 8.8.8.8.

This sounds like a issue with the ISP. Since they are going to ask you to do it anyway when you call make sure you power cycle the modem and the router.

Pretty standard tests. Ping your router IP to be sure you see no packet loss or high latency. This pretty much tests that you pc is ok and likely the router software and hardware.

Then ping a IP like 8.8.8.8 with a problem as bad as you report you should see packet loss or high latency even with a ping command.

What you might also do just to avoid a stupid ISP blaming google for the problem is run tracert 8.8.8.8. It is not likely going to show you the real problem because it does not run long enough. The main goal is to get the IP of routers in the path. You now want to test ping to the IP in hop 2. This is the ISP first router. Hopefully they have not rig it to not respond to ping.

The goal here is to show the ISP that ping is good to your router IP so everything is fine with your equipment but you see issue when you ping the ISP router.

There's definitely something wrong with the ISP, I feel. Today when I arrived home to check my PC, the internet speed went to 50mbs and now it's at 30-40mbs, it's fluctuating and I tested what you told me. I couldn't ping the hop 2 IP, it was timing out. As for the latency it was between 10 ms and 30 ms which was much better than this morning which was around 150 ms. I bought myself a new ethernet cable just to be sure it's not my old cable dying because wi-fi is at a stable 50 mbs.

Check the following.

right click the icon to the internet to the left of your speaker icon , click on change adapter options , right click your internet connection icon and choose properties , click on internet protocol v 4 to highlight it then properties , on the bottom half of the page you are looking at now , click on the button use the following dns , now in the first box you need 8 8 8 8 and in the second you need 8 8 4 4 , finally tick validate settings before exit .

I tried this, didn't really change anything but thank you.

 

[bill001g]

A bad ethernet cable generally does not have those symptoms. It is just a wire and the latency in a copper is wire is some fractional part of the speed of light, it is almost to small too small to calculate even at the 100 meter maximum ethernet cable lenth.

I could I suppose be getting lots of data errors but that too tends to be unlikely what commonly happens is the port will drop to 100mbps rather than run at 1gbit.

If you already have it no harm in trying it.

If hop 2 times out try hop 3 or whatever the first hop that will respond. Not as good as hop 2 but you have no control over this stuff. If the ISP is really stupid they might try to say it isn't there problem and because they prevent you from proving it is there problem. Hopefully they just agree to send someone to test and fix it.

Although not very likely you can try disabling IPv6 in the network interface. Something you can try while you wait for the ISP. IPv6 many times has a worst path though the internet and if you are now using IPv6 when before you were using IPv4 it could seem slower.

 

[MJS WARLORD]

This might not help you but its worth a quick look , go to settings then network and internet tab , this will take you to status , at the top it should show you are on ethernet and then click on where it says change adapter options , this should also show you are on ethernet , it should also show bluetooth and wi fi not connected.

The reason i am telling you this is because i once had a custom built pc that kept doing odd things whilst on the internet and it turned out that the builders had somehow put my settings on wi fi and i was using an ethernet cable.