Reason for frequent "Request Timed Out" when Pinging my DNS

[kaushikshepard]

I was facing a lot of lag recently on various programs so i pinged my DNS (8.8.8.8) and this is what i got (please refer to the above pictures). Actually this problem started recently (i did not change any hardware on my pc)
What happens is that many programs such as Skype, Viber, Whatsapp lags on a regular basis, and even when playing games on multiplayer, i face intermittent lag. These time outs occur even on my laptop when i pinged my DNS through it. I have a Binatone Wi-fi Router, but i took the above screenshots after disconnecting all devices.
Is this a problem with my ISP or should i check anything else?
Please if you could help, i am facing a lot of problems as video conferencing is almost impossible due to lag, even my download speeds are getting affected.

 

[bill001g]

This is generally due to packet loss in the path....where exactly is the key issue. Since the latency is fairly consistent it is more likely to be some like of errors on a line than a load related issue.

You can look at a program called pathping but I generally prefer to do it manually.

You want to run tracert to some location and then run continuous ping to a number of the nodes.

Unfortunately you will only be able to do something about the first couple devices in the traceroute. The first is your router which you have complete control over. The second generally represents your connection to the ISP which includes the wiring in your house. Anything past this is in the ISP network. When you get far down it can be another ISP so you need to hope it is in the first couple of hops of a trace.

 

[kaushikshepard]

This is generally due to packet loss in the path....where exactly is the key issue. Since the latency is fairly consistent it is more likely to be some like of errors on a line than a load related issue.

You can look at a program called pathping but I generally prefer to do it manually.

You want to run tracert to some location and then run continuous ping to a number of the nodes.

Unfortunately you will only be able to do something about the first couple devices in the traceroute. The first is your router which you have complete control over. The second generally represents your connection to the ISP which includes the wiring in your house. Anything past this is in the ISP network. When you get far down it can be another ISP so you need to hope it is in the first couple of hops of a trace.

Hi bill, thanks for replying.
I don't quite know how to pathping, so I'm not sure as to what i did, but i got this result when I pathpinged 8.8.8.8

 

[bill001g]

Your problem is you are seeing 10% loss starting in hop 2. This means there is some problem with your connection to the ISP. It can be your modem, the wiring in your house or something with the ISP wiring. You should check everything you can in your house and the call the ISP and have them come out and check.