latency jitter [38...300+]

[Swearinbag]

I have noticed a recently very annoying issue, that being that my ping has become very unstable, ranging from 39ms to 200+. I did a ping check to google.be (as I'm from Belgium) and got the following results:

https://imgur.com/a/1ZIl129

I'm using a powerline (TP-LINK) and it's fairly recent, have never had issues so I'm thinking it could be the router, but as far as I know, everything is normal..

I also did a tracert to google.be (just to see if the problem was from my pc-router-server connection and turns out that after my main modem, the latency jump happens... does this mean that my ISP is causing this or the modem?

[Referrences, all to the "google.be" ->] https://imgur.com/a/PL5EdA5

 

[bill001g]

Your tracert actually show no real problems. All the later hops in the trace are fine if there was a actual problem you would see delays in the later hops.

It does not really matter what intermediate hops get as long as it does not affect the traffic going to the the end. Ping and tracert are considered low priority traffic so a router in the path will delay responding to tracert or ping if it is busy passing actual useful data.

The problem with tracert and intermittent problems is there is not enough traffic so tracert does not catch it.

You could open multiple cmd windows and let constant ping run to every hop in the trace. You should see issues in all the windows at the same time....hopefully. You want to see if you can detect the hop the problem starts in and then continues in hops past it.

The farther from your house you get the harder it will be to get fixed. If it is in other ISP there is little you can do. If it is in your ISP you have a chance but must level 1 support guys do not know how to troubleshoot anything other than the equipment in your house and the connection to your house.

 

[Swearinbag]

Your tracert actually show no real problems. All the later hops in the trace are fine if there was a actual problem you would see delays in the later hops.

It does not really matter what intermediate hops get as long as it does not affect the traffic going to the the end. Ping and tracert are considered low priority traffic so a router in the path will delay responding to tracert or ping if it is busy passing actual useful data.

The problem with tracert and intermittent problems is there is not enough traffic so tracert does not catch it.

You could open multiple cmd windows and let constant ping run to every hop in the trace. You should see issues in all the windows at the same time....hopefully. You want to see if you can detect the hop the problem starts in and then continues in hops past it.

The farther from your house you get the harder it will be to get fixed. If it is in other ISP there is little you can do. If it is in your ISP you have a chance but must level 1 support guys do not know how to troubleshoot anything other than the equipment in your house and the connection to your house.

Hm, thanks for the info anyway! It's weird as it just happened a few days ago and already did troubleshoot my cables for bad ones and bad connections at which point I was pretty clueless.. I'll keep the threat open just for the sake it'll stay around

 

[Swearinbag]

Your tracert actually show no real problems. All the later hops in the trace are fine if there was a actual problem you would see delays in the later hops.

It does not really matter what intermediate hops get as long as it does not affect the traffic going to the the end. Ping and tracert are considered low priority traffic so a router in the path will delay responding to tracert or ping if it is busy passing actual useful data.

The problem with tracert and intermittent problems is there is not enough traffic so tracert does not catch it.

You could open multiple cmd windows and let constant ping run to every hop in the trace. You should see issues in all the windows at the same time....hopefully. You want to see if you can detect the hop the problem starts in and then continues in hops past it.

The farther from your house you get the harder it will be to get fixed. If it is in other ISP there is little you can do. If it is in your ISP you have a chance but must level 1 support guys do not know how to troubleshoot anything other than the equipment in your house and the connection to your house.

Hm, thanks for the info anyway! It's weird as it just happened a few days ago and already did troubleshoot my cables for bad ones and bad connections at which point I was pretty clueless.. I'll keep the threat open just for the sake it'll stay around