> a.nic.de is with RIPE in Amsterdam > f.nic.de and z.nic.de are in Frankfurt > c.de.net. is with Savvis in Santa Clara > s.de.net is with Deutsche Telekom in Germany > l.de.net I see over Mediaways/Telefonica DE in London (what a poor choice, scary)
For what it's worth, a highly scientific measurement from my house in Berkeley, the authoritative location for all quantitative evaluation of the Internet, using secret proprietary round-trip latency-measurement tools... a.nic.de, 100 packets, 7% packet loss round-trip min/avg/max = 163.454/199.368/494.708 ms c.de.net, 100 packets, 2% packet loss round-trip min/avg/max = 15.071/46.131/724.957 ms z.nic.de, 100 packets, 3% packet loss round-trip min/avg/max = 180.9/222.723/578.468 ms s.de.net, 100 packets, 0% packet loss round-trip min/avg/max = 184.26/219.786/501.547 ms l.de.net, 100 packets, 1% packet loss round-trip min/avg/max = 170.435/211.573/568.7 ms f.nic.de, 100 packets, 5% packet loss round-trip min/avg/max = 171.717/206.826/489.947 ms Overall for DENIC: 3% loss and 15ms / 166ms / 725ms min/avg/max latency. c.de.net is the one I'd be using, and it gives 2% loss and 46ms latency. a.gtld.biz, 100 packets, 1% packet loss round-trip min/avg/max = 91.234/122.828/504.932 ms b.gtld.biz, 100 packets, 2% packet loss round-trip min/avg/max = 84.284/113.632/391.781 ms c.gtld.biz, 100 packets, 0% packet loss round-trip min/avg/max = 11.425/34.311/351.397 ms d.gtld.biz, 100 packets, 3% packet loss round-trip min/avg/max = 151.251/189.494/592.378 ms e.gtld.biz, 100 packets, 8% packet loss round-trip min/avg/max = 183.608/222.593/571.288 ms f.gtld.biz, 100 packets, 4% packet loss round-trip min/avg/max = 191.292/220.594/501.575 ms g.gtld.biz, 100 packets, 0% packet loss round-trip min/avg/max = 73.427/98.744/272.382 ms h.gtld.biz, 100 packets, 0% packet loss round-trip min/avg/max = 11.389/17.377/62.261 ms Overall for Sentan: 2% loss and 11ms / 127ms / 592ms min/avg/max latency. h.gtld.biz is the one I'd be using, and it gives 0% loss and 17ms latency. a2.nstld.com, 100 packets, 0% packet loss round-trip min/avg/max = 75.234/105.418/428.176 ms c2.nstld.com, 100 packets, 9% packet loss round-trip min/avg/max = 74.604/99.534/355.924 ms d2.nstld.com, 100 packets, 1% packet loss round-trip min/avg/max = 106.717/144.679/459.303 ms e2.nstld.com, 100 packets, 0% packet loss round-trip min/avg/max = 24.709/63.391/602.586 ms f2.nstld.com, 100 packets, 34% packet loss round-trip min/avg/max = 30.717/65.595/365.876 ms g2.nstld.com, 100 packets, 1% packet loss round-trip min/avg/max = 14.06/61.24/380.896 ms l2.nstld.com, 100 packets, 1% packet loss round-trip min/avg/max = 72.493/112.227/852.949 ms Overall for Verisign: 7% loss and 14ms / 93ms / 852ms min/avg/max latency. g2.nstld.com is the one I'd be using, and it gives 1% loss and 61ms latency. This was just a test of the root DNS measurement system. Had this been a real measurement of the root DNS system, it would have been conducted by Nevil Brownlee, from his house in Auckland. -Bill