On 17.02.2012, at 17:12, Anurag Bhatia wrote:

Nice report Mirjam


Thanks for sharing. I found k-root to be having issues in India multiple times. Sometimes due to downtime of Delhi node

when exactly did you observe the Delhi node was down?


, other time due to messed up routing which takes off traffic outside India, increasing latency from 30ms to over 150ms.

That is difficult for us to remedy. But we can try if we get concrete reports.


I am curious to see RIPE probe collected data for the k-root.

http://atlas.ripe.net/contrib/rtt_maps.html?msm_id=1&proto=4&mapType=terrain&mapZoom=4&mapCenter=22.162665,74.718262

http://atlas.ripe.net/contrib/root_anycast.html?msm_id=1&proto=4&mapType=terrain&mapZoom=4&mapCenter=13.7078,74.356934

http://atlas.ripe.net/contrib/comparative_root_rtt.html?proto=46&mapType=terrain&mapZoom=4&mapCenter=21.151816,73.716064


http://dnsmon.ripe.net/dns-servmon/server/plot?server=k.root-servers.net;type=drops;tstart=1329400800;tstop=1329487199;af=ipv4