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

[Trex]

tracert to dns.google from 117 IP pool

1 2 ms 2 ms 2 ms 192.168.0.1
2 5 ms 3 ms 4 ms 117.241.140.1
3 4 ms 4 ms 4 ms 218.248.169.33
4 5 ms 5 ms 5 ms static.ill.218.248.107.114/24.bsnl.in [218.248.107.114]
5 * * * Request timed out.
6 * 6 ms 4 ms 117.216.207.203
7 7 ms 7 ms 7 ms 72.14.220.152
8 6 ms 6 ms 6 ms 172.253.69.191
9 5 ms 6 ms 6 ms 142.251.52.223
10 9 ms 9 ms 8 ms dns.google [8.8.8.8]

 

[Realme]

Can you post : one.one.one.one and mirror.nforce.com plz?

 

[Trex]

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

1 2 ms 2 ms 2 ms 192.168.0.1
2 4 ms 5 ms 4 ms 117.241.140.1
3 6 ms 3 ms 4 ms 218.248.169.33
4 6 ms 7 ms 4 ms static.ill.218.248.107.114/24.bsnl.in [218.248.107.114]
5 * 6 ms 6 ms 117.216.207.202
6 5 ms 5 ms 5 ms 117.216.207.203
7 7 ms 7 ms 5 ms 115.110.78.173
8 * * * Request timed out.
9 40 ms 39 ms 40 ms 115.114.85.222
10 41 ms 40 ms 39 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
11 * * * Request timed out.
12 49 ms 49 ms 57 ms 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
13 47 ms 47 ms 49 ms one.one.one.one [1.1.1.1]

 

[Trex]

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

1 3 ms 2 ms 3 ms 192.168.0.1
2 5 ms 3 ms 4 ms 117.241.140.1
3 4 ms 4 ms 6 ms 218.248.169.33
4 5 ms 5 ms 31 ms 218.248.162.150
5 * 6 ms 5 ms 117.216.207.202
6 7 ms 6 ms 5 ms 117.216.207.203
7 7 ms 7 ms 7 ms 125.21.44.229
8 154 ms 148 ms 150 ms 182.79.142.80
9 202 ms 180 ms 192 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
10 499 ms 183 ms 159 ms 185.107.116.1
11 159 ms 158 ms 158 ms mirror.nforce.com [85.159.239.121]

 

[Realme]

@Trex Based on your tracerts I am taking certain assumptions:

I did a tracert from different location which has same gateway as yours:
117.216.207.202
117.216.207.203

And ping from that locations are very bad just as others report.

Especially on this : 117.216.207.203 endpoint

Based on your pings which are quite good even when adjusting for your proximity to Delhi/Noida Region.

My belief is: Every Region(on the basis of state) has different port(s) on the REGIONAL router and for some of them region respective port(s) are choked as evident from fine pings from your end in contrast to different locations on the same gateways.

I pinged to other gateways IP on BSNL and I found that you don't need to go through 117.216.207.203 to reach them as BSNL has different routing for them.

And for those gateways pings were quite good

I will wait for tracerts from other to have a better diagnosis data

 

[Elavarasan]

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

1 6 ms 6 ms 1 ms 192.168.1.1
2 5 ms 2 ms 1 ms 117.197.176.1
3 2 ms 3 ms 2 ms 218.248.163.225
4 7 ms 7 ms 8 ms static.ill.218.248.113.86/24.bsnl.in [218.248.113.86]
5 * * * Request timed out.
6 * * * Request timed out.
7 39 ms 20 ms 29 ms 14.141.139.145.static-chennai.vsnl.net.in [14.141.139.145]
8 20 ms 21 ms 21 ms 172.29.209.114
9 22 ms 22 ms 22 ms 115.114.85.222
10 40 ms 41 ms 40 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
11 * * * Request timed out.
12 28 ms 28 ms 40 ms 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
13 27 ms 27 ms 38 ms one.one.one.one [1.1.1.1]

Tracing route to 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 3 ms 192.168.1.1
2 3 ms 2 ms 2 ms 117.197.176.1
3 3 ms 2 ms 11 ms 218.248.163.225
4 5 ms 10 ms 4 ms static.ill.218.248.108.118/24.bsnl.in [218.248.108.118]
5 * * 4 ms 117.216.207.214
6 * * * Request timed out.
7 36 ms 36 ms 38 ms 125.16.14.141
8 164 ms 164 ms 165 ms 182.79.154.147
9 234 ms 252 ms 238 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
10 236 ms 412 ms 248 ms 185.107.116.2
11 188 ms 182 ms 188 ms mirror.nforce.com [85.159.239.121]

Tracing route to mirror.nforce.com [85.159.239.121]

 

---

[Realme]

Elvasaran are you facing the same issue or you just contributed data? :')

 

[Elavarasan]

@Realme i just contributed the data. iam not facing that issue.

 

[Realme]

I felt that might be that might be the case from your tracert Elvasaran.

Thanks to you I achieved a goal of creating TTL expired in transit aka routing loops in BSNL

To other who were suffering the same issue: Have things improved for you by now? Please notify

 

[Trex]

What? I don't get it.