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,290
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 6 ms 7 ms 8 ms 10.212.138.1
3 7 ms 8 ms 8 ms 218.248.162.114
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 21 ms 16 ms 72.14.211.114
7 16 ms 17 ms 17 ms 74.125.242.145
8 17 ms 18 ms 18 ms 209.85.248.211
9 17 ms 17 ms 17 ms dns.google [8.8.8.8]

Trace complete.
--------------------------------------------------------------------------------------------------------------------------------------------------------

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 8 ms 8 ms 10.212.138.1
3 6 ms 6 ms 8 ms 218.248.169.78
4 * * * Request timed out.
5 * * * Request timed out.
6 23 ms 23 ms 22 ms 14.141.139.145.static-chennai.vsnl.net.in [14.141.139.145]
7 21 ms 21 ms 21 ms 172.29.209.114
8 21 ms 21 ms 21 ms 115.114.85.222
9 22 ms 22 ms 22 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
10 * * * Request timed out.
11 102 ms 39 ms 39 ms 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
12 38 ms 39 ms 39 ms one.one.one.one [1.1.1.1]

Trace complete.

----------------------------------------------------------------------------------------------------------------------------------------------------------

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 7 ms 6 ms 7 ms 10.212.138.1
3 9 ms 8 ms 8 ms 218.248.169.78
4 * * 16 ms 117.216.207.223
5 * 16 ms 16 ms 117.216.207.222
6 53 ms 50 ms 55 ms 125.17.212.249
7 177 ms 179 ms 178 ms 116.119.36.231
8 182 ms 200 ms 181 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
9 246 ms 182 ms 184 ms 185.107.116.1
10 182 ms 183 ms 182 ms mirror.nforce.com [85.159.239.121]

Trace complete.

-----------------------------------------------------------------------------------------------------------------------------------------------------------
 
Tracing route to dns.google [8.8.4.4]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 4 ms 4 ms 4 ms 59.91.104.1
3 5 ms 3 ms 4 ms 218.248.169.33
4 5 ms 4 ms 4 ms 218.248.169.38
5 6 ms 6 ms 6 ms 117.216.207.202
6 5 ms 5 ms 5 ms 117.216.207.203
7 7 ms 6 ms 5 ms 72.14.220.152
8 8 ms 8 ms 8 ms 108.170.237.85
9 6 ms 6 ms 5 ms 142.251.52.225
10 6 ms 8 ms 6 ms dns.google [8.8.4.4]
Click to expand...

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 4 ms 4 ms 59.91.104.1
3 5 ms 3 ms 4 ms 218.248.169.33
4 5 ms 5 ms 7 ms 218.248.169.38
5 * 7 ms 5 ms 117.216.207.202
6 * 6 ms 6 ms 117.216.207.203
7 5 ms 5 ms 5 ms 115.110.78.173
8 * * * Request timed out.
9 40 ms 40 ms 40 ms 115.114.85.222
10 246 ms 243 ms 243 ms 14.142.39.21.static-Mumbai.vsnl.net.in [14.142.39.21]
11 * * * Request timed out.
12 92 ms 50 ms 50 ms 121.240.243.210.STATIC-Mumbai.vsnl.net.in [121.240.243.210]
13 50 ms 48 ms 49 ms one.one.one.one [1.1.1.1]
Click to expand...

Tracing route to mirror.nforce.com [85.159.239.121]
over a maximum of 30 hops:
1 4 ms 2 ms 2 ms 192.168.0.1
2 4 ms 4 ms 4 ms 59.91.104.1
3 4 ms 5 ms 4 ms 218.248.169.33
4 5 ms 4 ms 4 ms 218.248.165.254
5 * 6 ms 7 ms 117.216.207.202
6 * 5 ms 6 ms 117.216.207.203
7 10 ms 9 ms 8 ms 125.21.44.229
8 135 ms 125 ms 126 ms 116.119.61.204
9 154 ms 158 ms 153 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
10 146 ms 147 ms 146 ms 185.107.116.2
11 146 ms 146 ms 146 ms mirror.nforce.com [85.159.239.121]
Click to expand...
 
One thing i don't understand, why latency to 1.1.1.1 high on BSNL. Earlier i was using local ISP SBR Telecom, which was giving me latency under 5ms to cloudflare. But with BSNL it is always above 40ms.
 
It all depends on peering and routing. The DE-CIX Mumbai has to be the point where your requests go for CF . It will increase the ping for you . Also BSNL Internal routing is not that efficient. Other ISP internal routing takes max of 10ms from Customer Router to External internet or the TATA route, whereas BSNL takes more,again not everywhere it happens like that. But it is there at some places

If Cloudflare and your ISP are directly peered at a point , then the latency reduces. BSNL goes through TATA I guess. Post a traceroute , we can analyze it
 
You must log in or register to reply here.
Back