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 3,928
Trex

Trex

This is the way
Messages
585
Location
Haryana Gurgaon
ISP
BSNL
The latency on 59.x.x.x is very high since a week but on 117.x.x.x it is very good. I have to reboot the router many times to get it on 117 IP pool. What should i do?
 
same thing is happening to me, this 59.x.x.x.x pool is too bad, currently there's nothing you can do except calling your nearest exchange and asking them to assign a static ip from a good pool like 117.x.x.x.x or you can just wait till BSNL fixes this problem
 
Yes, thinking to file complaint to their twitter handle. For now i disconnect and reconnect several times to get on 117 IP pool.
 
For me, 59.x.y.z and 61.x.y.z pools are terrible. They give ~20-25mbps speed tops and the latency is quite high.
117.x.y.z pool is decent..

I just disable my PPPoE connection until it gets the correct IP.
 
I am having the same issue as well . Pings on 117.216.x.x and 59.92.x.x are terrible but I get decent pings on 117.215.x.x , 59.96.x.x and 173.96.x.x. I have to restart my router until I get one of the good IP ranges.
 
BSNL regional BIG routers are overloaded I guess. I checked for Delhi and Mumbai region

If you guy can post tracert for dns.google (earlier it was handled to Airtel but now directly peer with BSNL at major centres say Delhi) and one.one.one.one (mumbai/tata vsnl routed) we can have better diagnosis.
 
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]
 
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]
 
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]
 
@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
 

Top