11/23/2011
Reading time: 4 mins

latency of the NTCs ADSL gateway from my home so high often request times out.

Why on earth is the latency of the  NTC's ADSL gateway from my home so high? Often the request times out,  Khatey NTC. I think over subscription is the reason behind this.

C:\Users\USER>ping 113.199.128.1 -t

Pinging 113.199.128.1 with 32 bytes of data:
Reply from 113.199.128.1: bytes=32 time=812ms TTL=254
Reply from 113.199.128.1: bytes=32 time=827ms TTL=254
Reply from 113.199.128.1: bytes=32 time=841ms TTL=254
Reply from 113.199.128.1: bytes=32 time=741ms TTL=254
Reply from 113.199.128.1: bytes=32 time=856ms TTL=254
Request timed out.
Reply from 113.199.128.1: bytes=32 time=760ms TTL=254
Reply from 113.199.128.1: bytes=32 time=543ms TTL=254
Reply from 113.199.128.1: bytes=32 time=705ms TTL=254
Reply from 113.199.128.1: bytes=32 time=798ms TTL=254
Reply from 113.199.128.1: bytes=32 time=626ms TTL=254
Reply from 113.199.128.1: bytes=32 time=830ms TTL=254
Reply from 113.199.128.1: bytes=32 time=615ms TTL=254
Reply from 113.199.128.1: bytes=32 time=617ms TTL=254
Reply from 113.199.128.1: bytes=32 time=938ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 113.199.128.1: bytes=32 time=819ms TTL=254
Reply from 113.199.128.1: bytes=32 time=842ms TTL=254
Reply from 113.199.128.1: bytes=32 time=1046ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 113.199.128.1: bytes=32 time=677ms TTL=254
Reply from 113.199.128.1: bytes=32 time=808ms TTL=254
Reply from 113.199.128.1: bytes=32 time=606ms TTL=254
Reply from 113.199.128.1: bytes=32 time=830ms TTL=254
Request timed out.
Request timed out.
Reply from 113.199.128.1: bytes=32 time=917ms TTL=254
Request timed out.
Reply from 113.199.128.1: bytes=32 time=1070ms TTL=254
Request timed out.
Request timed out.
Reply from 113.199.128.1: bytes=32 time=670ms TTL=254
Reply from 113.199.128.1: bytes=32 time=780ms TTL=254
Reply from 113.199.128.1: bytes=32 time=581ms TTL=254
Reply from 113.199.128.1: bytes=32 time=883ms TTL=254
Reply from 113.199.128.1: bytes=32 time=836ms TTL=254
Reply from 113.199.128.1: bytes=32 time=653ms TTL=254
Request timed out.
Reply from 113.199.128.1: bytes=32 time=523ms TTL=254
Reply from 113.199.128.1: bytes=32 time=570ms TTL=254
Reply from 113.199.128.1: bytes=32 time=575ms TTL=254
Reply from 113.199.128.1: bytes=32 time=877ms TTL=254
Reply from 113.199.128.1: bytes=32 time=716ms TTL=254
Request timed out.
Request timed out.
 

When pinged to google.com this happened

C:\Users\USER>ping google.com

Pinging google.com [74.125.236.52] with 32 bytes of data:
Reply from 74.125.236.52: bytes=32 time=885ms TTL=55
Request timed out.
Request timed out.
Reply from 74.125.236.52: bytes=32 time=634ms TTL=55

Ping statistics for 74.125.236.52:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 634ms, Maximum = 885ms, Average = 759ms
 

When tracert ing the google.com following happened

C:\Users\USER>tracert google.com

Tracing route to google.com [74.125.236.52]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     *        *       39 ms  1-adsl.ntc.net.np [113.199.128.1]
  3   688 ms   796 ms     *     202.70.66.26
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.

  6   140 ms   131 ms   125 ms  209.85.243.156
  7  1174 ms     *        *     66.249.94.75
  8     *        *        *     Request timed out.
  9   855 ms   609 ms   237 ms  maa03s04-in-f20.1e100.net [74.125.236.52]

Trace complete.
 

After some minutes it cools down back but still the ping is high(avg:136ms) for a WAN gateway.

C:\Users\USER>ping 113.199.128.1 -t

Pinging 113.199.128.1 with 32 bytes of data:
Reply from 113.199.128.1: bytes=32 time=283ms TTL=254
Reply from 113.199.128.1: bytes=32 time=42ms TTL=254
Reply from 113.199.128.1: bytes=32 time=93ms TTL=254
Reply from 113.199.128.1: bytes=32 time=40ms TTL=254
Reply from 113.199.128.1: bytes=32 time=83ms TTL=254
Reply from 113.199.128.1: bytes=32 time=63ms TTL=254
Reply from 113.199.128.1: bytes=32 time=120ms TTL=254
Reply from 113.199.128.1: bytes=32 time=93ms TTL=254
Reply from 113.199.128.1: bytes=32 time=685ms TTL=254
Request timed out.
Reply from 113.199.128.1: bytes=32 time=101ms TTL=254
Reply from 113.199.128.1: bytes=32 time=646ms TTL=254
Reply from 113.199.128.1: bytes=32 time=925ms TTL=254
Reply from 113.199.128.1: bytes=32 time=274ms TTL=254
Reply from 113.199.128.1: bytes=32 time=92ms TTL=254
Reply from 113.199.128.1: bytes=32 time=45ms TTL=254
Reply from 113.199.128.1: bytes=32 time=81ms TTL=254
Reply from 113.199.128.1: bytes=32 time=81ms TTL=254
Reply from 113.199.128.1: bytes=32 time=40ms TTL=254
Reply from 113.199.128.1: bytes=32 time=59ms TTL=254
Reply from 113.199.128.1: bytes=32 time=40ms TTL=254
Reply from 113.199.128.1: bytes=32 time=41ms TTL=254
Reply from 113.199.128.1: bytes=32 time=39ms TTL=254
Reply from 113.199.128.1: bytes=32 time=44ms TTL=254
Reply from 113.199.128.1: bytes=32 time=84ms TTL=254
Reply from 113.199.128.1: bytes=32 time=40ms TTL=254
Reply from 113.199.128.1: bytes=32 time=40ms TTL=254
Reply from 113.199.128.1: bytes=32 time=66ms TTL=254
Reply from 113.199.128.1: bytes=32 time=39ms TTL=254
Reply from 113.199.128.1: bytes=32 time=41ms TTL=254
Reply from 113.199.128.1: bytes=32 time=73ms TTL=254
Reply from 113.199.128.1: bytes=32 time=55ms TTL=254
Reply from 113.199.128.1: bytes=32 time=61ms TTL=254
Reply from 113.199.128.1: bytes=32 time=41ms TTL=254
Reply from 113.199.128.1: bytes=32 time=42ms TTL=254
Reply from 113.199.128.1: bytes=32 time=175ms TTL=254

Ping statistics for 113.199.128.1:
    Packets: Sent = 36, Received = 35, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 925ms, Average = 136ms
 

Previous
Drupal 7 Create node with node_add() in custom module
Next
jQuery – How can scroll UP/DOWN be distinguished??
© 2024 Anil Maharjan