File: why.jpg (56 KB, 500x500) Image search: [Google]

56 KB, 500x500

Why? How?

>be gaming
>be lagging randomly where I seem to be dropping bursts of packets for about 1 second and then its fine for 5 seconds then drop again
>open command prompt

Tracing route to xxx.xx.xxx.xx over a maximum of 30 hops

1 <1 ms 1 ms 1 ms xxx.xx.xxx.xx
2 1 ms 2 ms 1 ms xxx.xx.xxx.xx
3 4 ms 3 ms 2 ms xxx.xx.xxx.xx
4 7 ms 5 ms 10 ms xxx.xx.xxx.xx
5 1393 ms 794 ms 1136 ms zzz.zz.zzz.zz
6 817 ms 484 ms 246 ms xxx.xx.xxx.xx
7 426 ms 94 ms 796 ms xxx.xx.xxx.xxx

So hop five looks like the problem

Pinging zzz.zz.zzz.zz with 32 bytes of data:
Reply from zzz.zz.zzz: bytes=32 time=19ms TTL=60
Reply from zzz.zz.zzz. bytes=32 time=6ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=27ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=8ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=7ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=8ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=79ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=54ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=843ms TTL=60
Request timed out.
Reply from zzz.zz.zzz: bytes=32 time=11ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=55ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=7ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=6ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=5ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=8ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=19ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=1535ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=99ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=26ms TTL=60
Request timed out.
Reply from zzz.zz.zzz: bytes=32 time=439ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=106ms TTL=60
Reply from zzz.zz.zzz: bytes=32 time=9ms TTL=60


Why? What is this? Do all ISP's do this?

Is this the ISP throttling my traffic because they didn't buy enough bandwidth? Or is it a hardware issue?

Its not JUST dropped packets because some packets do get through just really fucking late.