Getting hight latency on 59.x.x.x IP pool since a week.

  • Thread starter Thread starter Trex
  • Start date Start date
  • Replies Replies 44
  • Views Views 4,103
Use OpenDNS or Google DNS if you can . They are peered better I guess. Geographically BSNL routing differs at places, so trial method is better
 
$ traceroute 1.1.1.1
1?: [LOCALHOST] pmtu 1460
1: 192.168.10.1 1.902ms
1: 192.168.10.1 4.383ms
2: 192.168.10.1 2.267ms pmtu 1452
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply
^C
Click to expand...
$ traceroute mirror.nforce.com
1?: [LOCALHOST] pmtu 1460
1: 192.168.10.1 2.670ms
1: 192.168.10.1 2.361ms
2: 192.168.10.1 27.051ms pmtu 1452
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
^C
Click to expand...

Used Tremux on my android phone to get these..
 
Hello..

So guess Termux didn't show any valuable data and I was in sleep didn't notice it too..

tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 11 ms 13 ms 19 ms 192.168.10.1
2 12 ms 16 ms 12 ms 10.212.200.1
3 14 ms 18 ms 13 ms static.ill.218.248.57.110/24.bsnl.in [218.248.57.110]
4 * 20 ms 19 ms 218.248.255.20
5 * * * Request timed out.
6 30 ms 34 ms 47 ms 115.110.229.45.static-mumbai.vsnl.net.in [115.110.229.45]
7 36 ms 28 ms 25 ms 172.23.78.233
8 58 ms 53 ms * 172.31.167.46
9 79 ms 72 ms 49 ms 115.114.85.222
10 245 ms 431 ms 318 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
11 * * * Request timed out.
12 56 ms 61 ms 64 ms 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
13 60 ms 61 ms 48 ms one.one.one.one [1.1.1.1]

Trace complete.
Click to expand...
Tracing route to mirror.nforce.com [85.159.239.121]
over a maximum of 30 hops:

1 18 ms 10 ms 8 ms 192.168.10.1
2 39 ms 26 ms 18 ms 10.212.200.1
3 27 ms 13 ms 14 ms static.ill.218.248.57.110/24.bsnl.in [218.248.57.110]
4 25 ms 31 ms 22 ms 218.248.255.20
5 * * * Request timed out.
6 17 ms 18 ms 18 ms aes-static-041.105.144.59.airtel.in [59.144.105.41]
7 136 ms 137 ms 137 ms 116.119.57.80
8 141 ms 141 ms 145 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
9 144 ms 148 ms 336 ms 185.107.116.2
10 167 ms 161 ms 163 ms mirror.nforce.com [85.159.239.121]

Trace complete.
Click to expand...
 

I am not facing any major issues but my results are different than of you guys if someone could explain it will be better

I tried multiple times on windows still the same result​

Trace-route Google DNS​

Tracing route to dns.google [8.8.4.4]
over a maximum of 30 hops:

1 <1 ms 4 ms 14 ms 192.168.1.1
2 7 ms 6 ms 1 ms 10.218.72.97
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 28 ms 27 ms 72.14.195.21
7 32 ms 33 ms 33 ms 74.125.242.145
8 33 ms 47 ms 34 ms 74.125.252.91
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

Tracing route to one.one.one.one [1.1.1.1]​

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms <1 ms <1 ms 10.218.72.97
3 2 ms 1 ms 1 ms static.ill.218.248.102.66/24.bsnl.in [218.248.102.66]
4 * * * Request timed out.
5 * * * Request timed out.
6 145 ms 146 ms 146 ms 115.110.161.209.static.vsnl.net.in [115.110.161.209]
7 147 ms 145 ms 147 ms 115.114.85.222
8 138 ms 140 ms 140 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
9 * * * Request timed out.
10 * 37 ms * 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

Tracing route to mirror.nforce.com [85.159.239.121]​

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms 8 ms <1 ms 10.218.72.97
3 3 ms 1 ms 1 ms static.ill.218.248.102.66/24.bsnl.in [218.248.102.66]
4 * * * Request timed out.
5 * * * Request timed out.
6 35 ms 41 ms 36 ms 125.16.14.141
7 147 ms 149 ms 147 ms 182.79.134.144
8 213 ms 202 ms 196 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
9 172 ms 172 ms 171 ms 185.107.116.2
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

But I got results when I did traceroute from Router Terminal​

google dns 30ms
1.1.1.1 dns 40ms
mirror.nforce 190ms

In both the cases I was in same IP pool
Click to expand...
 
Please use WinMTr(FREE) or Pingplotter(PAID) to generate tracert on Windows PC ( atleast wait for 100 seconds or 100 packets whichever is earlier)
 
I have switched to asianet fiber and here are the tracert results for comparison

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 172.17.105.1
3 8 ms 8 ms 11 ms 249.43.92.111.asianet.co.in [111.92.43.249]
4 8 ms 7 ms 7 ms 129.43.92.111.asianet.co.in [111.92.43.129]
5 19 ms 18 ms 17 ms nsg-static-9.59.75.182-airtel.com [182.75.59.9]
6 23 ms 18 ms 18 ms 116.119.68.247
7 18 ms 18 ms 18 ms 72.14.208.234
8 20 ms 20 ms 20 ms 108.170.226.93
9 19 ms 19 ms 19 ms 142.250.233.145
10 18 ms 18 ms 18 ms dns.google [8.8.8.8]

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 172.17.105.1
3 8 ms 16 ms 8 ms 249.43.92.111.asianet.co.in [111.92.43.249]
4 8 ms 8 ms 8 ms 129.43.92.111.asianet.co.in [111.92.43.129]
5 18 ms 17 ms 18 ms nsg-static-9.59.75.182-airtel.com [182.75.59.9]
6 19 ms 23 ms 18 ms 116.119.55.52
7 19 ms 18 ms 28 ms 182.79.161.171
8 18 ms 18 ms 18 ms one.one.one.one [1.1.1.1]

Tracing route to mirror.nforce.com [85.159.239.121]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 172.17.105.1
3 8 ms 8 ms 8 ms 249.43.92.111.asianet.co.in [111.92.43.249]
4 7 ms 8 ms 23 ms 129.43.92.111.asianet.co.in [111.92.43.129]
5 17 ms 18 ms 18 ms nsg-static-9.59.75.182-airtel.com [182.75.59.9]
6 149 ms 146 ms 147 ms 182.79.154.149
7 168 ms 168 ms 168 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
8 171 ms 170 ms 170 ms 185.107.116.2
9 169 ms 170 ms 170 ms mirror.nforce.com [85.159.239.121]
 

Similar threads

I
I Want to change my IP range from 117.x.x.x to 59.x.x.x
2
Replies
11
Views
4,398
invisiblex
A
Force 59.x.x.x IP
Replies
7
Views
3,551
adi.1994
ckr97
BSNL Broadband: Connection getting reset on IP 117.x.x.x (earlier no such problem with 59.x.x.x)
2 3 4
Replies
36
Views
15,309
ckr97
B
High Speed in 59.x.x.x or 117.x.x.x?
Replies
7
Views
6,143
baluchen
Back