Strange Latency Problem

  • Thread starter Thread starter rsen
  • Start date Start date
  • Replies Replies 6
  • Views Views 1,602
R

rsen

Regular
Messages
150
Location
NA
ISP
Bsnl
For the last 2 weeks I have had a very strange problem with latencies especially to servers in the EU and US.

Usually; say I start off with a 290ms latency to servers in the US.
After about an hour - maybe less or more; slowly this latency will increase by about 100ms to say 370-390ms.

Now if I repeatedly reconnect using different dns servers on my internet connection dialer there is a fair chance that the latency will go back to normal after about 4-5 tries.

Here's a ping snippet where my latency was awful then i disconnect and reconnect twice to get back to normal latencies:

Code: 
Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=365ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=367ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=367ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=313ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=287ms TTL=50Reply from 66.199.244.82: bytes=32 time=292ms TTL=50Reply from 66.199.244.82: bytes=32 time=285ms TTL=50Reply from 66.199.244.82: bytes=32 time=294ms TTL=50Reply from 66.199.244.82: bytes=32 time=285ms TTL=50Reply from 66.199.244.82: bytes=32 time=288ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=292ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=287ms TTL=50Reply from 66.199.244.82: bytes=32 time=288ms TTL=50
However even after doing this the latency problem slowly creeps in yet again after a completely random length of time typically between 15 minutes to 45 minutes and the latencies are back to being sh*t.

All of this doesn't seem to have much of a correlation on whether or not I'm downloading or torrenting anything.

I have used namebench to pick a good dns server and each time it changes. Regardless I have set up dialers for each of these servers; but the problem crops up in all of them.

1 more thing whenever the latency goes up like this my internet browsing speed goes down significantly with webpages often getting stuck loading.
 
I think some problem from ur ISP. I too had problem like this, so disconnected my internet
 
Even worse now @ 7:16am

Disconnecting and reconnecting seem to alternate between latencies of 372ms to 464ms to US servers when it was 280 only 20 minutes ago.

Code: 
Reply from 66.199.244.82: bytes=32 time=459ms TTL=52Reply from 66.199.244.82: bytes=32 time=457ms TTL=52Reply from 66.199.244.82: bytes=32 time=460ms TTL=52Reply from 66.199.244.82: bytes=32 time=453ms TTL=52Reply from 66.199.244.82: bytes=32 time=462ms TTL=52Reply from 66.199.244.82: bytes=32 time=456ms TTL=52Reply from 66.199.244.82: bytes=32 time=453ms TTL=52Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=454ms TTL=52Reply from 66.199.244.82: bytes=32 time=451ms TTL=52Reply from 66.199.244.82: bytes=32 time=462ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=382ms TTL=52Reply from 66.199.244.82: bytes=32 time=379ms TTL=52Reply from 66.199.244.82: bytes=32 time=380ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=455ms TTL=52Reply from 66.199.244.82: bytes=32 time=460ms TTL=52Reply from 66.199.244.82: bytes=32 time=467ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=373ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=375ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=377ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=376ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=375ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Reply from 66.199.244.82: bytes=32 time=454ms TTL=52Reply from 66.199.244.82: bytes=32 time=456ms TTL=52Reply from 66.199.244.82: bytes=32 time=457ms TTL=52Reply from 66.199.244.82: bytes=32 time=459ms TTL=52Reply from 66.199.244.82: bytes=32 time=458ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Request timed out.Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Request timed out.Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52
"Destination net unreachable." is where I am disconnecting and re-connecting.

----------

https://www.speedtest.net

Speed to US servers is also really bad right now; this is at the 371ms latency above.

----------

Speed to London server:
https://www.speedtest.net

----------

To tokyo server https://www.speedtest.net

----------

to dhaka:
https://www.speedtest.net
not sure how a server this close can give such awful results.

----------

Traceroute to Product reviews and prices, software downloads, and tech news - CNET

Tracing route to phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]
over a maximum of 30 hops:
Code: 
  1    10 ms    49 ms    29 ms  59.93.192.1  2    52 ms    53 ms    51 ms  218.248.255.42  3    85 ms    54 ms    49 ms  59.163.206.177.static.chennai.vsnl.net.in [59.163.206.177]  4    70 ms    69 ms    71 ms  172.31.16.1735   112 ms    69 ms    71 ms  if-0-100.tcore2.MLV-Mumbai.as6453.net [180.87.39.25]  6   316 ms   349 ms   323 ms  if-6-2.tcore1.L78-London.as6453.net [80.231.130.5]  7     *      327 ms   361 ms  Vlan704.icore1.LDN-London.as6453.net [80.231.130.10]  8   369 ms   369 ms   403 ms  Vlan533.icore1.LDN-London.as6453.net [195.219.83.102]  9   391 ms   373 ms   373 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]10   378 ms   435 ms   369 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]11   368 ms   365 ms   371 ms  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]12   368 ms   375 ms   397 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]13   374 ms   369 ms   385 ms  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]14   416 ms   413 ms   405 ms  ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 15   406 ms   405 ms   405 ms  ae-92-92.csw4.Dallas1.Level3.net [4.69.151.165]16   409 ms     *      428 ms  ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]17   439 ms   437 ms   439 ms  ae-1-8.bar1.Phoenix1.Level3.net [4.69.133.29] 18   450 ms   449 ms   451 ms  ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]19   444 ms   465 ms   447 ms  ae-5-5.car2.Phoenix1.Level3.net [4.69.148.121] 20   442 ms   445 ms   439 ms  CBS-CORPORA.car2.Phoenix1.Level3.net [4.53.106.146] 21     *      477 ms   453 ms  64.30.227.11822   484 ms   439 ms   439 ms  phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]Trace complete.
 
For the last 2 weeks I have had a very strange problem with latencies especially to servers in the EU and US.

Usually; say I start off with a 290ms latency to servers in the US.
After about an hour - maybe less or more; slowly this latency will increase by about 100ms to say 370-390ms.

Now if I repeatedly reconnect using different dns servers on my internet connection dialer there is a fair chance that the latency will go back to normal after about 4-5 tries.

Here's a ping snippet where my latency was awful then i disconnect and reconnect twice to get back to normal latencies:

Code: 
Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=365ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=367ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=367ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=313ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=287ms TTL=50Reply from 66.199.244.82: bytes=32 time=292ms TTL=50Reply from 66.199.244.82: bytes=32 time=285ms TTL=50Reply from 66.199.244.82: bytes=32 time=294ms TTL=50Reply from 66.199.244.82: bytes=32 time=285ms TTL=50Reply from 66.199.244.82: bytes=32 time=288ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=292ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=286ms TTL=50Reply from 66.199.244.82: bytes=32 time=287ms TTL=50Reply from 66.199.244.82: bytes=32 time=288ms TTL=50
However even after doing this the latency problem slowly creeps in yet again after a completely random length of time typically between 15 minutes to 45 minutes and the latencies are back to being sh*t.

All of this doesn't seem to have much of a correlation on whether or not I'm downloading or torrenting anything.

I have used namebench to pick a good dns server and each time it changes. Regardless I have set up dialers for each of these servers; but the problem crops up in all of them.

1 more thing whenever the latency goes up like this my internet browsing speed goes down significantly with webpages often getting stuck loading.

Even worse now @ 7:16am

Disconnecting and reconnecting seem to alternate between latencies of 372ms to 464ms to US servers when it was 280 only 20 minutes ago.

Code: 
Reply from 66.199.244.82: bytes=32 time=459ms TTL=52Reply from 66.199.244.82: bytes=32 time=457ms TTL=52Reply from 66.199.244.82: bytes=32 time=460ms TTL=52Reply from 66.199.244.82: bytes=32 time=453ms TTL=52Reply from 66.199.244.82: bytes=32 time=462ms TTL=52Reply from 66.199.244.82: bytes=32 time=456ms TTL=52Reply from 66.199.244.82: bytes=32 time=453ms TTL=52Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=454ms TTL=52Reply from 66.199.244.82: bytes=32 time=451ms TTL=52Reply from 66.199.244.82: bytes=32 time=462ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=382ms TTL=52Reply from 66.199.244.82: bytes=32 time=379ms TTL=52Reply from 66.199.244.82: bytes=32 time=380ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=455ms TTL=52Reply from 66.199.244.82: bytes=32 time=460ms TTL=52Reply from 66.199.244.82: bytes=32 time=467ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=373ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=375ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=377ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=376ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=375ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=464ms TTL=52Reply from 66.199.244.82: bytes=32 time=454ms TTL=52Reply from 66.199.244.82: bytes=32 time=456ms TTL=52Reply from 66.199.244.82: bytes=32 time=457ms TTL=52Reply from 66.199.244.82: bytes=32 time=459ms TTL=52Reply from 66.199.244.82: bytes=32 time=458ms TTL=52Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Request timed out.Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=378ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Request timed out.Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=374ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=368ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=370ms TTL=52Reply from 66.199.244.82: bytes=32 time=369ms TTL=52Request timed out.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 192.168.1.1: Destination net unreachable.Reply from 66.199.244.82: bytes=32 time=371ms TTL=52Reply from 66.199.244.82: bytes=32 time=372ms TTL=52Reply from 66.199.244.82: bytes=32 time=371ms TTL=52
"Destination net unreachable." is where I am disconnecting and re-connecting.

----------

https://www.speedtest.net

Speed to US servers is also really bad right now; this is at the 371ms latency above.

----------

Speed to London server:
https://www.speedtest.net

----------

To tokyo server https://www.speedtest.net

----------

to dhaka:
https://www.speedtest.net
not sure how a server this close can give such awful results.

----------

Traceroute to Product reviews and prices, software downloads, and tech news - CNET

Tracing route to phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]
over a maximum of 30 hops:
Code: 
  1    10 ms    49 ms    29 ms  59.93.192.1  2    52 ms    53 ms    51 ms  218.248.255.42  3    85 ms    54 ms    49 ms  59.163.206.177.static.chennai.vsnl.net.in [59.163.206.177]  4    70 ms    69 ms    71 ms  172.31.16.1735   112 ms    69 ms    71 ms  if-0-100.tcore2.MLV-Mumbai.as6453.net [180.87.39.25]  6   316 ms   349 ms   323 ms  if-6-2.tcore1.L78-London.as6453.net [80.231.130.5]  7     *      327 ms   361 ms  Vlan704.icore1.LDN-London.as6453.net [80.231.130.10]  8   369 ms   369 ms   403 ms  Vlan533.icore1.LDN-London.as6453.net [195.219.83.102]  9   391 ms   373 ms   373 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]10   378 ms   435 ms   369 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]11   368 ms   365 ms   371 ms  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]12   368 ms   375 ms   397 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]13   374 ms   369 ms   385 ms  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]14   416 ms   413 ms   405 ms  ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 15   406 ms   405 ms   405 ms  ae-92-92.csw4.Dallas1.Level3.net [4.69.151.165]16   409 ms     *      428 ms  ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]17   439 ms   437 ms   439 ms  ae-1-8.bar1.Phoenix1.Level3.net [4.69.133.29] 18   450 ms   449 ms   451 ms  ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]19   444 ms   465 ms   447 ms  ae-5-5.car2.Phoenix1.Level3.net [4.69.148.121] 20   442 ms   445 ms   439 ms  CBS-CORPORA.car2.Phoenix1.Level3.net [4.53.106.146] 21     *      477 ms   453 ms  64.30.227.11822   484 ms   439 ms   439 ms  phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]Trace complete.

Your pings of
 
Thanks.Yeah 300-330ms to US east is definitely reasonable and understandable. It's just that occasionally latencies shoot up to 480+ms and this happens quite often at various times during the day especially during the early morning 7am-8am period.These times are accompanied by very low bandwidth and intermittent packet loss so getting anything done becomes a pain.As you said it's probably because of peak times in the US. However what's strange is whenever I get sh*tty routing to the US, EU routes also seem to be awful. I can't understand how it can be peak times at both places at the same time.Or perhaps it's just outgoing congestion from India to the EU/US region ?I've tried connecting to US west servers but they give almost the same and occasionally worse latencies than US East. Perhaps BSNL routes US west thru the NYC area ?150-200ms to San hose sounds amazing and almost too good to be true (with bsnl at least lol) but I'll definitely look at servers there.
 
Thanks.
Yeah 300-330ms to US east is definitely reasonable and understandable.
It's just that occasionally latencies shoot up to 480+ms and this happens quite often at various times during the day especially during the early morning 7am-8am period.
These times are accompanied by very low bandwidth and intermittent packet loss so getting anything done becomes a pain.

As you said it's probably because of peak times in the US.
However what's strange is whenever I get sh*tty routing to the US, EU routes also seem to be awful. I can't understand how it can be peak times at both places at the same time.
Or perhaps it's just outgoing congestion from India to the EU/US region ?

I've tried connecting to US west servers but they give almost the same and occasionally worse latencies than US East. Perhaps BSNL routes US west thru the NYC area ?
150-200ms to San hose sounds amazing and almost too good to be true (with bsnl at least lol) but I'll definitely look at servers there.

It could be possible that BSNL is routing much of it's US traffic these days via Europe because it now has a share in the Europe-India gateway and it would surely be much cheaper for them to do so (at the expense of good routing to the US), but not being a BSNL customer and thus unable to do any diagnosis, I can only speculate on what they might be doing: this assumption is purely based on the trace-route you've provided in a previous post.

On the other hand, they're sending an awful lot of traffic to US backbones (Savvis, GlobalCrossing, GlobeInternet) so it's difficult to say who is at fault (the Internet can be a funny animal). In the trace provided, that traffic is being handed over to Tata/VSNL in Mumbai and on to Level3 in London, so it's got less to do with BSNL and more to do with Tata in this case because there is almost zero additional latency coming from Level3, it's all Tata. Based on that trace, there every chance that whoever is hosting Cnet.com isn't buying from the 3 providers mentioned above.
 

Strangely enough airtel routes most traffic to the US via pacific route through the west coast; although latencies there are higher on average than BSNL (when they keep their sh*t together, that is).
Airtel also seems to use less congested routes typically and very little packet loss if ever. Airtel also seems a lot less vulnerable to jitter and congestion or bad routing issues.
However Airtel has FUP and comes out to be almost double in terms of costs.

Kolkata doesn't seem to be many alternatives at all so I'm stuck with BSNL and a crappy airtel backup. Neither reliance or anyone else wants to setup shop here.

Hopefully more ISP's will eventually come here.

This is from today; after 8am; and It's 1:13am IST now so it's probably off-peak everywhere (early morning US early evening EU i think).
BSNL:
Code: 
Tracing route to phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]over a maximum of 30 hops:  1     9 ms     9 ms    11 ms  59.93.240.1  2    42 ms    41 ms    41 ms  218.248.255.30  3    48 ms    49 ms    47 ms  59.163.206.45.static.chennai.vsnl.net.in [59.163.206.45]  4    74 ms    73 ms    73 ms  172.31.16.173  5    74 ms    73 ms    73 ms  if-0-100.tcore2.MLV-Mumbai.as6453.net [180.87.39.25]  6   324 ms   325 ms   325 ms  if-6-2.tcore1.L78-London.as6453.net [80.231.130.5]  7   336 ms   327 ms   337 ms  Vlan704.icore1.LDN-London.as6453.net [80.231.130.10]  8   268 ms   267 ms   267 ms  Vlan533.icore1.LDN-London.as6453.net [195.219.83.102]  9   278 ms   277 ms   271 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120] 10   270 ms   269 ms   269 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141] 11   270 ms   267 ms   269 ms  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78] 12   278 ms   271 ms   269 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70] 13   270 ms   269 ms   269 ms  ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37] 14   306 ms   305 ms   305 ms  ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 15   319 ms   311 ms   311 ms  ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153] 16   307 ms   305 ms   305 ms  ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150] 17   339 ms   337 ms   337 ms  ae-1-8.bar1.Phoenix1.Level3.net [4.69.133.29] 18   350 ms   351 ms   349 ms  ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114] 19   340 ms   339 ms   339 ms  ae-5-5.car2.Phoenix1.Level3.net [4.69.148.121] 20   340 ms   339 ms   339 ms  CBS-CORPORA.car2.Phoenix1.Level3.net [4.53.106.146] 21   346 ms   345 ms   343 ms  64.30.227.118 22   340 ms   339 ms   341 ms  phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]Trace complete.
pings to cnet itself are excellent in the 268-276ms range.

Now here's airtel:
Code: 
Tracing route to phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]over a maximum of 30 hops:  1    28 ms    29 ms    25 ms  ABTS-North-Static-136.237.160.122.airtelbroadband.in [122.160.237.136]  2    26 ms    25 ms    25 ms  ABTS-North-Static-237.237.160.122.airtelbroadband.in [122.160.237.237]  3    26 ms    25 ms    25 ms  AES-Static-021.78.22.125.airtel.in [125.22.78.21]  4   110 ms   109 ms   301 ms  182.79.255.14  5   116 ms   125 ms   125 ms  Vlan562.icore1.SVQ-Singapore.as6453.net [120.29.215.73]  6   100 ms    99 ms    99 ms  if-9-1807.tcore2.SVW-Singapore.as6453.net [120.29.215.30]  7   356 ms   297 ms   297 ms  if-7-2.tcore2.LVW-LosAngeles.as6453.net [180.87.15.26]  8   323 ms   323 ms   323 ms  xe-8-0-0.edge1.LosAngeles9.Level3.net [4.68.62.117]  9   343 ms   345 ms   345 ms  vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254] 10   328 ms   329 ms   329 ms  ae-92-92.ebr2.LosAngeles1.Level3.net [4.69.137.29] 11   348 ms   385 ms   349 ms  ae-1-4.bar2.Phoenix1.Level3.net [4.69.133.37] 12   338 ms   337 ms   337 ms  ae-5-5.car2.Phoenix1.Level3.net [4.69.148.121] 13   340 ms   339 ms   339 ms  CBS-CORPORA.car2.Phoenix1.Level3.net [4.53.106.166] 14   332 ms   333 ms   329 ms  64.30.227.54 15   334 ms   333 ms   333 ms  phx1-rb-gtm1-tron-xw-lb.cnet.com [64.30.224.103]Trace complete.
pings with airtel are in the 332-335ms range; and routing in this case is via the pacific/west coast. Slightly less jitter too.

----------

I think one of the biggest frustrations for me is :

1) There aren't any alternatives in Kolkata other than bsnl and airtel
2) Sometimes when the internet takes a massive dump; it seems like there is no one to talk to to get it fixed and tier 3 tech support is non-existent. Call center operators naturally have no clue about routing or latency issues 🙁
 

Top