Hi,
I am using AS38536 Software Technology Parks of India, which uses TATA for all internet routing and traffic.
On this network 1.1.1.1 is not working at all and 1.0.0.1 is having high latency.
Ping works for both with 100ms+ latency but traceroute to 1.1.1.1 fails.
Please check test results below.
Traceroute @1.1.1.1
Results
1 203.193.179.17 0.266 ms 0.297 ms 0.274 ms
2 14.141.172.221 1.758 ms * 3.139 ms
Traceroute @1.0.0.1
Results
1 203.193.179.17 0.355 ms 0.280 ms 0.264 ms
2 14.141.172.221 1.802 ms 1.765 ms 1.636 ms
3 172.31.134.205 19.791 ms 19.521 ms 19.853 ms
4 172.29.251.34 55.071 ms 55.052 ms 55.105 ms
5 180.87.37.1 54.377 ms 54.358 ms 59.886 ms
6 180.87.37.14 96.522 ms 98.430 ms
180.87.37.65 104.145 ms
7 180.87.12.1 99.996 ms 101.516 ms 99.990 ms
8 180.87.98.37 98.515 ms 98.452 ms 104.736 ms
9 120.29.214.90 98.949 ms 98.966 ms 98.596 ms
10 1.0.0.1 98.871 ms 96.830 ms 98.268 ms
There are additional reports of problems in India, would you mind following this guide as closely as possible and posting (copy and paste would be ideal) the results here?
The same problem in BSNL Fiber because BSNL uses Tata communications for peering . So i am reached Tata communications in twitter to peer with Cloudflare
Now Cloudflare can peer with Tata communications, i guess (if not possible)
In my observation, Tata communications Mumbai peers with Cloudflare,
Tata communications Chennai loosing peering with Cloudflare and routing request from Chennai to Mumbai and it leading to 20-30ms more latency then normal.
@cloonan You can peer with Tata communication Chennai and fix this problem.
