Hello everyone!
Seems like Tata Communications routing table is changed (call it fixed) to route traffic for openDNS to Singapore. It’s not going to London anymore and I see very good latency from BSNL too (which uses Tata Comm for most of it’s International traffic).
Here’s latest routing from BSNL to openDNS:Â
HOST: laptop                                 Loss%  Snt  Last  Avg  Best  Wrst StDev
 1. router2                                     0.0%   50   2.0  1.7  1.5  2.2  0.2
 2. 117.207.48.1                               2.0%   50  25.4  26.2  24.5  36.1  1.6
 3. 218.248.173.38                             0.0%   50  26.1  31.2  25.0 125.5  17.8
 4. 121.244.68.114.static-lvsb.vsnl.net.in        2.0%   50  70.1  72.2  69.4  97.8  6.0
 5. 172.31.61.210                               0.0%   50  92.9  94.8  92.9 109.0  2.2
 6. ix-4-2.tcore1.CXR-Chennai.as6453.net       0.0%   50  94.3  98.4  93.1 154.6  12.6
 7. if-5-2.tcore1.SVW-Singapore.as6453.net      0.0%   50  127.2 130.6 125.8 165.5  8.5
 8. if-2-2.tcore2.SVW-Singapore.as6453.net     0.0%   50  126.8 128.6 124.4 178.2  8.3
 9. Vlan1807.icore1.SVQ-Singapore.as6453.net  2.0%   50  135.4 132.3 126.1 140.4  4.4
 10. 203.208.186.101                            0.0%   50  202.4 163.6 156.9 256.5  17.5
 11. 203.208.153.110                            0.0%   50  159.1 166.8 157.0 272.4  23.6
 12. 203.208.190.166                            2.0%   50  160.3 160.6 158.6 191.9  4.6
 13. resolver1.opendns.com                      2.0%   50  159.0 158.3 156.9 162.4  1.0
Overall I am getting latency from 160ms which seems OK considering 25-30ms latency for DSL, adding 60-90ms for route till South India followed by 30-40ms latency between Chennai and Singapore and eventually destination openDNS node on ASN 36692.Â
Oh and btw I was lucky enough to meet DNS godfather David Ulevitch at openDNS HQ in San Francisco during last US trip. A very impressive personality!
Â
Well that’s all for now. Will be posting a couple more updates soon. Have a good week ahead!