We are now serving DNS traffic from our new datacenter in Amsterdam.

Please let us know if you see your traffic hitting Amsterdam or if you think you should be reaching the site and aren't.

Congrats on getting AMS up and running. Is there any timeline for when LA, DFW and MIA will be opened up as well?

Located in The Netherlands also going to London still.

1 private
2 private
3 23 ms 23 ms 23 ms lo1.dr5.d12.xs4all.net [194.109.5.219]
4 22 ms 22 ms 21 ms 0.ge-3-3-0.xr4.1d12.xs4all.net [194.109.7.157]
5 22 ms 21 ms 21 ms asd-dc2-ias-ur10.nl.kpn.net [194.151.244.74]
6 25 ms 24 ms 24 ms asd-dc2-ipc-dr02.nl.kpn.net [195.190.227.239]
7 25 ms 25 ms 23 ms 195.190.233.99
8 24 ms 24 ms 24 ms rt-dc2-ias-csg01.nl.kpn.net [195.190.227.196]
9 25 ms 25 ms 26 ms r22.amstnl02.nl.bb.gin.ntt.net [195.69.144.36]
10 35 ms 34 ms 48 ms p64-2-0-0.r23.londen03.uk.bb.gin.ntt.net [129.25
0.4.104]
11 33 ms 33 ms 34 ms po-5.r01.londen03.uk.bb.gin.ntt.net [129.250.5.2
38]
12 31 ms 32 ms 32 ms 83.231.146.198
13 31 ms 32 ms 32 ms resolver1.opendns.com [208.67.222.222]

@unoriginal
"Is there any timeline for when LA, DFW and MIA will be opened up as well?"
This was off-topic here. This is about Amsterdam. Here you go:
http://forums.opendns.com/comments.php?DiscussionID=4661&page=1#Item_6

I'm not routed to Amsterdam, too.

From Germany (t-online):

traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 40 byte packets
1 xxxxx (xxx.xxx.xxx.xxx) 14.687 ms 0.677 ms 0.663 ms
2 217.0.116.169 (217.0.116.169) 8.050 ms 40.615 ms 31.815 ms
3 217.0.67.210 (217.0.67.210) 87.891 ms 7.887 ms 8.104 ms
4 f-eb5-i.F.DE.NET.DTAG.DE (62.154.16.194) 19.314 ms 25.912 ms 19.534 ms
5 62.156.128.98 (62.156.128.98) 17.569 ms 15.430 ms 42.331 ms
6 xe-5-0-0.r20.frnkge03.de.bb.gin.ntt.net (129.250.3.221) 31.784 ms 18.833 ms 37.119 ms
7 as-0.r22.londen03.uk.bb.gin.ntt.net (129.250.2.226) 38.813 ms 43.935 ms 32.683 ms
8 po-4.r01.londen03.uk.bb.gin.ntt.net (129.250.5.234) 38.742 ms 41.412 ms 40.885 ms
9 83.231.146.198 (83.231.146.198) 66.777 ms 31.426 ms 30.902 ms
10 * * *

From Germany (interoute):

traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 40 byte packets
1 xxxxx (xxx.xxx.xxx.xxx) 0.573 ms 0.484 ms 0.432 ms
2 r5ffm.de.vianw.net (194.231.190.1) 19.341 ms 14.497 ms 14.990 ms
3 r2ffm.de.vianw.net (212.168.1.222) 15.013 ms 15.083 ms 15.006 ms
4 xe-10-0-0-205.fra-006-score-2-re0.interoute.net (89.202.163.249) 15.469 ms 15.588 ms 14.982 ms
5 ge-0.de-cix.frnkge03.de.bb.gin.ntt.net (80.81.192.46) 15.989 ms 15.995 ms 15.474 ms
6 xe-1-0-0.r20.frnkge03.de.bb.gin.ntt.net (129.250.2.148) 16.269 ms 20.262 ms 16.460 ms
7 as-0.r22.londen03.uk.bb.gin.ntt.net (129.250.2.226) 28.292 ms 28.672 ms 28.515 ms
8 po-4.r01.londen03.uk.bb.gin.ntt.net (129.250.5.234) 28.293 ms 28.103 ms 28.532 ms
9 83.231.146.198 (83.231.146.198) 28.559 ms 28.361 ms 29.464 ms
10 * * *

From Switzerland (cablecom). This is routed to Washington now!

traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 40 byte packets
1 * * *
2 217.168.57.109 (217.168.57.109) 12.198 ms 12.112 ms 11.256 ms
3 ch-zrh01a-ra1-ge-1-1-0.aorta.net (213.46.171.49) 12.967 ms 10.964 ms 14.391 ms
4 ch-gva01a-ra1-ge-0-1-0.aorta.net (213.46.171.9) 16.824 ms
213.46.171.61 (213.46.171.61) 28.365 ms
ch-gva01a-ra1-ge-0-1-0.aorta.net (213.46.171.9) 45.467 ms
5 fr-par02a-rd1-ge-1-0-0.aorta.net (213.46.160.25) 28.343 ms
fr-par02a-rd1-ge-15-0-0.aorta.net (213.46.160.49) 49.259 ms
fr-par02a-rd1-ge-1-0-0.aorta.net (213.46.160.25) 27.908 ms
6 us-was02a-rd1-pos-1-0.aorta.net (213.46.160.106) 110.651 ms 132.616 ms 125.495 ms
7 us-was02a-ri1-10ge-1-0-0-0.aorta.net (213.46.190.194) 106.164 ms 110.423 ms 109.535 ms
8 gi7-44.mpd01.iad01.atlas.cogentco.com (154.54.12.85) 132.837 ms 127.372 ms 270.715 ms
9 opendns.demarc.cogentco.com (38.104.56.50) 113.816 ms 131.425 ms 112.149 ms
10 * * *

I reach London OpenDNS with Cogent Co .
1 x
2 x
3 x
4 1 ms 1 ms 2 ms gi9-11.ccr01.buh01.atlas.cogentco.com [149.6.50.65]
5 22 ms 23 ms 22 ms te4-8.ccr01.bts01.atlas.cogentco.com [130.117.1.77]
6 31 ms 31 ms 32 ms te2-7.ccr01.muc01.atlas.cogentco.com [130.117.0.42]
7 36 ms 36 ms 36 ms te2-2.ccr01.fra03.atlas.cogentco.com [130.117.0.65]
8 47 ms 46 ms 47 ms te3-2.ccr01.par01.atlas.cogentco.com [130.117.2.54]
9 56 ms 56 ms 55 ms te2-7.ccr01.lon01.atlas.cogentco.com [130.117.2.166]
10 53 ms 53 ms 54 ms te4-4.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 57 ms 55 ms 54 ms opendns.demarc.cogentco.com [149.6.146.158]
12 54 ms 55 ms 53 ms resolver1.opendns.com [208.67.222.222]

Getting routed to London via Amsterdam, d'oh.

From both my server and home network in Germany.

Confirmed:

T-Online:
1 2 ms 1 ms 1 ms t-kiste_701 [192.168.2.1]
2 9 ms 7 ms 8 ms 217.0.118.160
3 20 ms 8 ms 7 ms 87.186.248.50
4 8 ms 8 ms 9 ms f-eb5-i.F.DE.NET.DTAG.DE [62.154.17.58]
5 9 ms 8 ms 9 ms 62.156.128.142
6 10 ms 9 ms 8 ms xe-5-0-0.r20.frnkge03.de.bb.gin.ntt.net [129.250.3.221]
7 22 ms 23 ms 23 ms as-0.r22.londen03.uk.bb.gin.ntt.net [129.250.2.226]
8 24 ms 23 ms 24 ms po-4.r01.londen03.uk.bb.gin.ntt.net [129.250.5.234]
9 24 ms 24 ms 24 ms 83.231.146.198
10 25 ms 25 ms 25 ms dns1.speedport.ip [208.67.222.222]

Cityweb:
1 9 ms 8 ms 8 ms rtsl-manz-de05.nw.mediaways.net [62.52.52.76]
2 9 ms 8 ms 8 ms xmws-manz-de02-chan-16.nw.mediaways.net [195.71.134.142]
3 9 ms 8 ms 8 ms rmws-manz-de02-xe-1-0-0-0.nw.mediaways.net [213.20.253.98]
4 25 ms 24 ms 24 ms rmws-lond-uk02-pos-0-1-0.nw.mediaways.net [195.71.236.250]
5 29 ms 24 ms 34 ms ge-1.linx.londen03.uk.bb.gin.ntt.net [195.66.226.138]
6 25 ms 24 ms 24 ms po-5.r01.londen03.uk.bb.gin.ntt.net [129.250.5.238]
7 167 ms 372 ms 373 ms 83.231.146.198
8 25 ms 25 ms 25 ms dns1.speedport.ip [208.67.222.222]

Likely a problem with your ISP, or a network it peers with. Timeout on the first hop is your connectivity to your ISP. (Momentary bad signal?)

"Well, I always get this same output even though the connection (a HSDPA mobile internet), is always working normally."

OK, it just takes longer than the default timeout to connect normally - no worries here then.

10.243.169.109 - You are being routed to one of the IANA Blackhole servers! Not good. (10.243.178.30 is a Blackhole as well.) I'm thinking that maybe Vipnet doesn't like traceroute and is blackholing this. (Of course it will continue to time out - you get no response from a black hole.) Try a traceroute to some other well known site, or perhaps a few, and see if the same thing happens.

OK, although this might mean nothing (since there're two different ISPs) just out of curiosity I connected my desktop PC with my old slow (i.e. the 28 kbps one using phone line) and not-used-anymore dial-up connection, btw. under Connection Properties Status its Server IP Address was: as6.voljatel.si (217.72.64.166) and Client IP Address was: vo170-68.dial-up.volja.net (217.72.68.170), and run a trace route using it.

And this is the trace route output:

C:\\->tracert resolver1.opendns.com

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

1 178 ms 155 ms 167 ms as6.voljatel.si [217.72.64.166]
2 147 ms 167 ms 155 ms cartman.voljatel.si [217.72.64.131]
3 219 ms 179 ms 179 ms 77.111.1.141
4 159 ms 191 ms 191 ms 77.111.1.130
5 159 ms 155 ms * 77.111.1.174
6 176 ms 335 ms 297 ms fra15-tus-telecom-1.fra.seabone.net [89.221.34.117]
7 169 ms 203 ms 179 ms ge-0.de-cix.frnkge03.de.bb.gin.ntt.net [80.81.192.46]
8 195 ms 263 ms 193 ms xe-1-0-0.r20.frnkge03.de.bb.gin.ntt.net [129.250.2.148]
9 211 ms 587 ms 215 ms as-0.r22.londen03.uk.bb.gin.ntt.net [129.250.2.226]
10 880 ms 826 ms 946 ms po-4.r01.londen03.uk.bb.gin.ntt.net [129.250.5.234]
11 207 ms 215 ms 215 ms 83.231.146.198
12 207 ms 203 ms 203 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

This trace route apparently completed (reached the destination) without any problem/time-outs. But from what I read I am still using London (and not in Amsterdam) datacenter. By the way, I am located in Ljubljana, Slovenia.

No, not Amsterdam, but just the USA...

Trace from German T-COM DSL Business connection (near Frankfurt/Main):

1 <1 ms <1 ms <1 ms dslrtr.xxx.xxx [internal]
2 156 ms 82 ms 49 ms 217.5.98.185
3 55 ms 47 ms 62 ms 217.5.100.234
4 154 ms 153 ms 50 ms f-eb5-i.F.DE.NET.DTAG.DE [62.154.16.198]
5 159 ms 52 ms 49 ms 62.156.128.142
6 54 ms 52 ms 74 ms xe-5-0-0.r20.frnkge03.de.bb.gin.ntt.net [129.250.3.221]
7 97 ms 71 ms 99 ms as-0.r22.londen03.uk.bb.gin.ntt.net [129.250.2.226]
8 156 ms 105 ms 357 ms po-4.r01.londen03.uk.bb.gin.ntt.net [129.250.5.234]
9 172 ms 169 ms 109 ms 83.231.146.198
10 73 ms 79 ms 125 ms resolver1.opendns.com [208.67.222.222]
------------------------------------------------------------------------

Well ... it´s still London:

nslookup -type=txt which.opendns.com. 208.67.222.222
Server: resolver1.opendns.com
Address: 208.67.222.222
which.opendns.com text = "3.lon"

Address: 208.67.220.220
which.opendns.com text = "4.lon"

Would be cool to save a few miles and get stuff resolves in Amsterdam

Cheers

"Is there any way to force the route to be 'refreshed' of 'forced' to Amsterdam?"
No, OpenDNS use Anycast.

"Or is it a ISP issue?"
Rather not. If you look back in the thread, most people of different ISPs are not routed to Amsterdam, but still to London.

It still is: http://system.opendns.com/

Can we expect some ping latency decrease here in Europe when Amsterdam server goes "really" online?

Is there a way to ping different opendns locations (London, Chicago, etc)?

I am not sure that I understand you!

vojkan:
rotblitz means for you to look back over this thread for the relevant post. This is the comment:

""Is there any way to force the route to be 'refreshed' of 'forced' to Amsterdam?"
No, OpenDNS use Anycast."

Anycast is your answer - no, you cannot ping a specific geolocation.

You're welcome.

Here an other trace route from german ISP KabelBW, it is routet to amsterdam:

Routenverfolgung zu resolver1.opendns.com [208.67.222.222] über maximal 30 Absch
nitte:

1 1 ms 1 ms <1 ms 192.168.0.1
2 * * * Zeitüberschreitung der Anforderung.
3 7 ms 20 ms 7 ms 172.30.25.41
4 67 ms * 35 ms 172.30.25.253
5 50 ms 40 ms 42 ms ae0.STR-M2.ip-bb.kabel-badenwuerttemberg.de [78.42.40.5]
6 42 ms 42 ms 43 ms ae1.FRA-M2.ip-bb.kabel-badenwuerttemberg.de [78.42.40.15]
7 41 ms 46 ms 44 ms HSI-KBW-091-089-091-002.hsi2.kabelbw.de [91.89.91.2]
8 58 ms 49 ms 53 ms xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]
9 41 ms 42 ms 37 ms opendns-gw.ip4.tinet.net [77.67.66.70]
10 61 ms 47 ms * resolver1.opendns.com [208.67.222.222]
11 39 ms 34 ms 44 ms resolver1.opendns.com [208.67.222.222]

Ablaufverfolgung beendet.

Any status updates on the Amsterdam routing?
I'm still getting routed from Norway to a US server.

Whose "mistake" is this state?

Interesting detail.

USA, going to 11.ams, co worker of mine on other side of town going to 12.ams.

you would think we would go to nyc or wdc.

bdavenport@atlantis:~$ sudo traceroute -A 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
1 10.10.10.1 (10.10.10.1) [AS65534] 6.362 ms 6.724 ms 7.124 ms
2 * * *
3 s66-76-168-197.bssr.suddenlink.net (66.76.168.197) [AS22773] 22.622 ms 22.960 ms 23.301 ms
4 s66-76-168-53.bssr.suddenlink.net (66.76.168.53) [AS22773] 28.933 ms 29.277 ms 29.619 ms
5 cdm-66-76-30-93.tylrtx.suddenlink.net (66.76.30.93) [AS19108/AS22773] 35.969 ms 36.692 ms 37.377 ms
6 cdm-66-76-30-81.tylrtx.suddenlink.net (66.76.30.81) [AS19108/AS22773] 36.289 ms 22.782 ms 22.604 ms
7 cdm-66-76-31-134.lfkn.suddenlink.net (66.76.31.134) [AS19108/AS22773] 24.066 ms 24.726 ms 25.731 ms
8 4-3.r1.dc.hwng.net (69.16.190.205) [AS11588] 29.609 ms 29.948 ms 30.290 ms
9 2-3.r2.dc.hwng.net (69.16.190.26) [AS11588] 26.046 ms 26.397 ms 1-1.r1.am.hwng.net (69.16.191.61) [AS11588] 136.750 ms
10 1-1.r2.am.hwng.net (69.16.191.122) [AS11588] 135.494 ms 135.848 ms 135.104 ms
11 peer1.rtr1.ams.opendns.com (195.69.144.88) [AS1200] 107.411 ms 107.035 ms 136.094 ms
12 * * *
13 * * *
14 * * *

Sadly, it's not a perfect science. LINX / London has so many peers and networks connected to us that it gets the bulk of our traffic. We are slowing bringing up more networks in Amsterdam so the problem will continue to get better. That said, a difference of maybe 10 extra ms to hit London won't impact folks in any noticeable way.