The team here has been hard at work over the past few months getting a new datacenter set up, and I’m happy to report that as of today, our Singpore datacenter is online and serving production OpenDNS traffic. The Singapore server marks our 12th datacenter globally and the first of a number planned for Asia.
One of the benefits of OpenDNS is that we use a technique called Anycast routing in how we run our network. Anycast means that no matter where you are in the world, your DNS requests route through our closest datacenter. And when we do maintenance that requires us to take a site offline, our routing topology ensures you will route to our next closest datacenter. It also means that when we bring up a new datacenter that is closer to you, your DNS requests will automatically start routing to it. So for the bulk of our users in Singapore, Thailand, Vietnam, India and throughout Asia, this new Singapore datacenter promises an even faster Internet.
And here’s a photo of what our installation looks like as it was being racked:
This Singapore datacenter is only the start. We’re planning on adding a new datacenter in Frankfurt, Germany in early 2011. After that, the plan is to continue expanding our footprint from there. As always, you can take a look at our global system status on our Systems page.
PS — Internet routing is not a perfect science and requires a lot of work to get right. If you are in Asia and a traceroute doesn’t show you talking to Singapore for DNS we want to know! Please send a traceroute from your computer to 208.67.222.222 to our support department so we can see which networks in Asia aren’t seeing our new routes.
Tommy Chandra W
Dear OpenDNS…
This traceroute come from my lappy. I come from Pontianak, Kalimantan Barat, Indonesia. Using internet from Telkom Indonesia.
C:\Users\Tommy>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 2 ms 2 ms 5 ms 192.168.222.1
2 8 ms 10 ms 4 ms 192.168.125.253
3 6 ms 4 ms 4 ms 172.255.1.1
4 87 ms 59 ms 49 ms 1.subnet110-139-102.speedy.telkom.net.id [110.13
9.102.1]
5 159 ms 113 ms 85 ms PE-PON-HUAWEI.telkom.net.id [125.160.1.77]
6 * * * Request timed out.
7 138 ms * 432 ms 61.subnet118-98-59.astinet.telkom.net.id [118.98
.59.61]
8 285 ms 263 ms 234 ms 61.5.51.61
9 * 124 ms 164 ms 118.98.0.234
10 213 ms 147 ms 199 ms 203.208.143.173
11 230 ms 128 ms * ge-0-1-8-0.sngtp-dr2.ix.singtel.com [203.208.151
.193]
12 104 ms 103 ms 103 ms 203.208.152.209
13 154 ms 143 ms 133 ms so-3-0-1-0.hkgcw-cr3.ix.singtel.com [203.208.151
.82]
14 150 ms 145 ms 151 ms so-3-0-0-0.hkgcw-cr4.ix.singtel.com [203.208.172
.182]
15 * 228 ms 162 ms 203.208.152.194
16 107 ms 150 ms 107 ms 116.51.17.210
17 114 ms 103 ms 131 ms resolver1.opendns.com [208.67.222.222]
You’re in S’pore. Great
posted on November 17th, 2010 at 7:42 am
Tommy Chandra W
Dear OpenDNS…
Different result when I trace to your secondary DNS resolver :
C:\Users\Tommy>tracert 208.67.220.220
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.222.1
2 9 ms 8 ms 15 ms 192.168.125.253
3 5 ms 5 ms 9 ms 172.255.1.1
4 59 ms 79 ms 102 ms 1.subnet110-139-102.speedy.telkom.net.id
9.102.1]
5 128 ms 57 ms 65 ms PE-PON-HUAWEI.telkom.net.id [125.160.1.77
6 * * * Request timed out.
7 * * 126 ms 61.subnet118-98-59.astinet.telkom.net.id
.59.61]
8 84 ms 64 ms 70 ms 61.5.51.61
9 93 ms * 93 ms 118.98.0.234
10 * 206 ms 109 ms 203.208.143.173
11 * 136 ms 148 ms ge-1-1-6-0.sngtp-dr1.ix.singtel.com [203.
.5]
12 119 ms 141 ms 122 ms 203.208.152.217
13 99 ms 130 ms 111 ms 203.208.151.250
14 209 ms 185 ms 187 ms 203.208.152.194
15 333 ms 358 ms 392 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net
0.6.97]
16 254 ms 207 ms 112 ms 116.51.17.210
17 122 ms 104 ms 178 ms 116.51.17.210
18 114 ms 106 ms 111 ms resolver2.opendns.com [208.67.220.220]
Trace complete.
Thanks…
posted on November 17th, 2010 at 7:54 am
LJ Phua
User from Singapore, ISP Singnet
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 23 ms 23 ms 30 ms bb116-14-180-1.singnet.com.sg [116.14.180.1]
2 22 ms * 23 ms 202.166.121.41
3 21 ms 22 ms 23 ms ge-3-0-0-3700.stella.singnt.com.sg [202.166.124.
105]
4 24 ms 22 ms 23 ms xe-0-0-0.singha.singnet.com.sg [202.166.120.13]
5 20 ms 23 ms 23 ms ae5-0.beck.singnet.com.sg [202.166.126.41]
6 22 ms 23 ms 22 ms 203.208.190.57
7 21 ms 23 ms 23 ms 203.208.152.209
8 25 ms 54 ms 23 ms 203.208.151.250
9 53 ms 60 ms 53 ms so-0-0-3-0.lonlx-cr2.ix.singtel.com [203.208.154
.22]
10 73 ms 76 ms 56 ms 203.208.152.194
11 74 ms 70 ms 70 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
12 70 ms 74 ms 73 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
ping is a lil slower then i had hope.. but fast enough to warrant a change in dns servers from google/local.
posted on November 17th, 2010 at 8:40 am
Andrea
Congratulations to OpenDNS for the excellent work and for the great service! I look forward to an Italian point of Frankfurt Datacenter to improve latency with OpenDNS
Rilevazione instradamento verso resolver1.opendns.com [208.67.222.222]
su un massimo di 30 punti di passaggio:
1
posted on November 17th, 2010 at 8:42 am
Harken
1 16 ms 8 ms 14 ms cm1.zeta20.maxonline.com.sg [116.87.20.1]
2 13 ms 59 ms 78 ms 172.20.35.1
3 44 ms 39 ms 58 ms 172.26.35.1
4 63 ms 30 ms 10 ms 172.20.7.18
5 91 ms 56 ms 11 ms 172.20.7.70
6 94 ms 76 ms 61 ms 203.116.17.65
7 52 ms 67 ms 48 ms 203.118.3.226
8 240 ms 217 ms 223 ms so-7-0-1.edge6.SanJose1.Level3.net [4.53.22.1]
9 220 ms 222 ms 216 ms ae-21-69.car1.SanJose2.Level3.net [4.68.18.11]
10 374 ms 274 ms 288 ms SPLICE-COMM.car1.SanJose2.Level3.net [4.59.0.174
]
11 219 ms 267 ms 229 ms resolver1.opendns.com [208.67.222.222]
posted on November 17th, 2010 at 9:20 am
Mohammad Niaz Morshed
Hi, I’m from Dhaka, Bangladesh. Glad to hear this news. Here is my trace route result:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Shovon>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on November 17th, 2010 at 10:06 am
Phoenix
Hi I am from India – both 208.67.222.222 and 220.220 are routing still to UK
??
is the isp responsible for this routing?
==
tracert -d 208.67.222.222
Tracing route to 208.67.222.222 over a maximum of 30 hops
1 40 ms 39 ms 40 ms 59.92.128.1
2 60 ms 59 ms 59 ms 218.248.255.6
3 62 ms 61 ms 63 ms 59.163.206.161
4 51 ms 52 ms 51 ms 172.31.4.93
5 54 ms 53 ms 52 ms 172.31.4.93
6 297 ms 303 ms 304 ms 116.0.84.41
7 293 ms 293 ms 292 ms 116.0.79.13
8 294 ms 293 ms 292 ms 116.0.79.26
9 290 ms 284 ms * 209.58.105.70
10 * * * Request timed out.
11 292 ms 282 ms 281 ms 4.68.110.213
12 278 ms 278 ms 282 ms 4.69.139.193
13 283 ms 281 ms 280 ms 4.69.143.109
14 252 ms 247 ms 311 ms 4.69.139.74
15 436 ms 320 ms 317 ms 195.50.122.86 UK
16 268 ms 272 ms 272 ms 208.67.222.222
Trace complete.
==
Tracing route to 208.67.220.220 over a maximum of 30 hops
1 38 ms 40 ms 40 ms 59.92.128.1
2 51 ms 50 ms 52 ms 218.248.255.82
3 52 ms 52 ms 52 ms 59.163.206.189
4 52 ms 51 ms 51 ms 59.163.55.245
5 52 ms 52 ms 52 ms 59.163.55.245
6 281 ms 286 ms 283 ms 116.0.84.41
7 299 ms 291 ms 356 ms 116.0.84.2
8 279 ms 265 ms 260 ms 116.0.79.26
9 * 284 ms 285 ms 209.58.105.70
10 * 291 ms * 195.219.241.69
11 292 ms 292 ms 292 ms 4.68.110.213
12 297 ms 298 ms 296 ms 4.69.139.193
13 302 ms 293 ms 299 ms 4.69.143.105
14 292 ms 289 ms 344 ms 4.69.139.74
15 559 ms 325 ms 317 ms 195.50.122.86 UK
16 292 ms 292 ms 296 ms 208.67.220.220
Trace complete.
posted on November 17th, 2010 at 11:43 am
David Ulevitch, Founder/CEO
Harken — We will try to fix this for you.
posted on November 17th, 2010 at 2:48 pm
Anand
Welcome to Singapore, OpenDNS!
From a singnet (one of the largest but braindead) ISP here:
ping times:
anand@bumblebee:~ Thu Nov 18-10:54:44 $ ping 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_req=1 ttl=51 time=170 ms
64 bytes from 208.67.222.222: icmp_req=2 ttl=51 time=101 ms
64 bytes from 208.67.222.222: icmp_req=3 ttl=51 time=87.4 ms
64 bytes from 208.67.222.222: icmp_req=4 ttl=51 time=88.4 ms
64 bytes from 208.67.222.222: icmp_req=5 ttl=51 time=86.7 ms
anand@bumblebee:~ Thu Nov 18-10:53:01 $ traceroute 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.879 ms 2.454 ms 2.524 ms
2 bb116-15-165-1.singnet.com.sg (116.15.165.1) 24.148 ms 28.185 ms 28.227 ms
3 202.166.121.249 (202.166.121.249) 28.346 ms 28.465 ms 28.602 ms
4 ge-3-0-0-3500.sapporo.singnet.com.sg (202.166.124.153) 28.825 ms 29.069 ms 29.705 ms
5 xe-2-2-0-0.budweiser.singnet.com.sg (202.166.126.9) 38.545 ms 38.566 ms 38.635 ms
6 ae1-0.beck.singnet.com.sg (202.166.124.234) 38.764 ms 26.423 ms 10.686 ms
7 203.208.190.57 (203.208.190.57) 10.797 ms 11.368 ms 11.408 ms
8 203.208.152.205 (203.208.152.205) 15.213 ms 15.390 ms 203.208.152.209 (203.208.152.209) 15.621 ms
9 so-3-0-3-0.hkgcw-cr3.ix.singtel.com (203.208.154.38) 45.210 ms 47.637 ms 46.294 ms
10 203.208.152.194 (203.208.152.194) 48.559 ms 203.208.152.154 (203.208.152.154) 65.151 ms 203.208.152.194 (203.208.152.194) 65.206 ms
11 203.208.152.194 (203.208.152.194) 65.475 ms 65.513 ms 77.786 ms
12 116.51.17.210 (116.51.17.210) 106.767 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 107.153 ms 116.51.17.210 (116.51.17.210) 90.182 ms
13 116.51.17.210 (116.51.17.210) 91.068 ms * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
anand@bumblebee:~
posted on November 17th, 2010 at 7:56 pm
Joachim
Frankfurt will be a great improvement for the German Users.
Good work!
And welcome to Singapure/Asia OpenDNS-Users
posted on November 17th, 2010 at 11:31 pm
Choojai
That’s great news for south east asia. I hope you coming to Thailand too.
posted on November 18th, 2010 at 12:23 am
Eduardo Arciga
I’m from Philippines and here is my result for my tracert:
C:\Documents and Settings\SERVER001>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 68 ms 53 ms 56 ms 124.105.29.254.pldt.net [124.105.29.254]
2 65 ms 58 ms 62 ms 124.107.254.118.pldt.net [124.107.254.118]
3 55 ms 65 ms 62 ms 124.83.5.153.pldt.net [124.83.5.153]
4 58 ms 54 ms 65 ms 210.213.133.34.static.pldt.net [210.213.133.34]
5 67 ms 77 ms 55 ms 210.213.128.58.static.pldt.net [210.213.128.58]
6 54 ms 54 ms 54 ms 210.213.129.25.static.pldt.net [210.213.129.25]
7 57 ms 57 ms 56 ms 210.213.128.25.static.pldt.net [210.213.128.25]
8 54 ms 53 ms 55 ms 210.213.130.5.static.pldt.net [210.213.130.5]
9 245 ms 246 ms 248 ms p4-2-1-0.r02.sttlwa01.us.bb.gin.ntt.net [129.250
.10.169]
10 251 ms 250 ms 247 ms po-4.r00.sttlwa01.us.bb.gin.ntt.net [129.250.3.6
9]
11 230 ms 230 ms 231 ms ge-1-13.r00.sttlwa01.us.ce.gin.ntt.net [129.250.
12.78]
12 230 ms 228 ms 229 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
C:\Documents and Settings\SERVER001>tracert 208.67.220.220
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1 41 ms 41 ms 42 ms 124.105.29.254.pldt.net [124.105.29.254]
2 44 ms 47 ms 80 ms 124.107.254.118.pldt.net [124.107.254.118]
3 42 ms 55 ms 42 ms 124.83.5.153.pldt.net [124.83.5.153]
4 42 ms 47 ms 44 ms 210.213.133.38.static.pldt.net [210.213.133.38]
5 43 ms 45 ms 53 ms 210.213.128.66.static.pldt.net [210.213.128.66]
6 128 ms 106 ms 107 ms 210.213.129.25.static.pldt.net [210.213.129.25]
7 43 ms 81 ms 89 ms 210.213.128.25.static.pldt.net [210.213.128.25]
8 72 ms 59 ms 46 ms 210.213.130.5.static.pldt.net [210.213.130.5]
9 275 ms 242 ms 316 ms p4-2-1-0.r02.sttlwa01.us.bb.gin.ntt.net [129.250
.10.169]
10 234 ms 235 ms 235 ms po-4.r00.sttlwa01.us.bb.gin.ntt.net [129.250.3.6
9]
11 227 ms 221 ms 232 ms ge-1-13.r00.sttlwa01.us.ce.gin.ntt.net [129.250.
12.78]
12 216 ms 220 ms 216 ms resolver2.opendns.com [208.67.220.220]
Trace complete.
posted on November 18th, 2010 at 2:08 am
installster
From Indonesia:
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 40 byte packets
1 ip3-17.cbn.net.id (202.158.3.17) 0.316 ms 0.407 ms 0.462 ms
2 210.210.161.1.cbn.net.id (210.210.161.1) 0.417 ms 0.405 ms 0.445 ms
3 210.210.161.134.cbn.net.id (210.210.161.134) 0.414 ms 0.446 ms 0.549 ms
4 202.158.31.130 (202.158.31.130) 3.573 ms 3.624 ms 3.614 ms
5 121.100.4.1 (121.100.4.1) 0.609 ms 0.665 ms 0.713 ms
6 121.100.5.5 (121.100.5.5) 19.163 ms 15.651 ms 18.987 ms
7 if-1-152.core1.SVQ-Singapore.as6453.net (216.6.93.25) 15.554 ms 15.538 ms 15.527 ms
8 if-2-2-0-0.tcore1.SVW-Singapore.as6453.net (180.87.12.9) 226.755 ms 226.728 ms 226.680 ms
9 if-15-0-0-1758.core2.S9R-Singapore.as6453.net (180.87.12.38) 16.640 ms 16.645 ms 16.627 ms
10 if-3-1-0.mcore3.PDI-PaloAlto.as6453.net (216.6.29.125) 196.768 ms 194.760 ms 194.744 ms
11 if-15-0-0-820.core4.SQN-SanJose.as6453.net (216.6.30.41) 184.972 ms 184.515 ms 184.323 ms
12 * * *
13 ix-2-0.icore1.SQN-SanJose.as6453.net (209.58.116.14) 181.549 ms 184.463 ms 184.433 ms
14 ae-31-99.car1.SanJose2.Level3.net (4.68.18.203) 185.881 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75) 186.338 ms 185.021 ms
15 SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174) 190.494 ms 187.963 ms 190.395 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
posted on November 18th, 2010 at 2:10 am
Eduardo Arciga
I’m from Philippines and here is my result for my tracert:
C:\Documents and Settings\SERVER001>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 68 ms 53 ms 56 ms 124.105.29.254.pldt.net [124.105.29.254]
2 65 ms 58 ms 62 ms 124.107.254.118.pldt.net [124.107.254.118]
3 55 ms 65 ms 62 ms 124.83.5.153.pldt.net [124.83.5.153]
4 58 ms 54 ms 65 ms 210.213.133.34.static.pldt.net [210.213.133.34]
5 67 ms 77 ms 55 ms 210.213.128.58.static.pldt.net [210.213.128.58]
6 54 ms 54 ms 54 ms 210.213.129.25.static.pldt.net [210.213.129.25]
7 57 ms 57 ms 56 ms 210.213.128.25.static.pldt.net [210.213.128.25]
8 54 ms 53 ms 55 ms 210.213.130.5.static.pldt.net [210.213.130.5]
9 245 ms 246 ms 248 ms p4-2-1-0.r02.sttlwa01.us.bb.gin.ntt.net [129.250
.10.169]
10 251 ms 250 ms 247 ms po-4.r00.sttlwa01.us.bb.gin.ntt.net [129.250.3.6
9]
11 230 ms 230 ms 231 ms ge-1-13.r00.sttlwa01.us.ce.gin.ntt.net [129.250.
12.78]
12 230 ms 228 ms 229 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
C:\Documents and Settings\SERVER001>tracert 208.67.220.220
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1 41 ms 41 ms 42 ms 124.105.29.254.pldt.net [124.105.29.254]
2 44 ms 47 ms 80 ms 124.107.254.118.pldt.net [124.107.254.118]
3 42 ms 55 ms 42 ms 124.83.5.153.pldt.net [124.83.5.153]
4 42 ms 47 ms 44 ms 210.213.133.38.static.pldt.net [210.213.133.38]
5 43 ms 45 ms 53 ms 210.213.128.66.static.pldt.net [210.213.128.66]
6 128 ms 106 ms 107 ms 210.213.129.25.static.pldt.net [210.213.129.25]
7 43 ms 81 ms 89 ms 210.213.128.25.static.pldt.net [210.213.128.25]
8 72 ms 59 ms 46 ms 210.213.130.5.static.pldt.net [210.213.130.5]
9 275 ms 242 ms 316 ms p4-2-1-0.r02.sttlwa01.us.bb.gin.ntt.net [129.250
.10.169]
10 234 ms 235 ms 235 ms po-4.r00.sttlwa01.us.bb.gin.ntt.net [129.250.3.6
9]
11 227 ms 221 ms 232 ms ge-1-13.r00.sttlwa01.us.ce.gin.ntt.net [129.250.
12.78]
12 216 ms 220 ms 216 ms resolver2.opendns.com [208.67.220.220]
Trace complete.
posted on November 18th, 2010 at 2:17 am
Vijay
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms menu [192.168.1.254]
2 18 ms 19 ms 21 ms bb116-14-108-1.singnet.com.sg [116.14.108.1]
3 18 ms 19 ms 19 ms te3-0-1-3450.sake.singnet.com.sg [202.166.122.81
]
4 18 ms 19 ms 19 ms xe-0-0-0-3000.qt-ar04.singnet.com.sg [202.166.12
1.129]
5 18 ms 21 ms 21 ms xe-0-2-0-3412.sherry.singnet.com.sg [202.166.120
.117]
6 18 ms 19 ms 19 ms ae6-0.singha.singnet.com.sg [202.166.120.186]
7 18 ms 19 ms 21 ms ae5-0.beck.singnet.com.sg [202.166.126.41]
8 20 ms 19 ms 19 ms 203.208.190.57
9 17 ms 19 ms 19 ms 203.208.152.205
10 51 ms 19 ms 51 ms so-3-0-1-0.hkgcw-cr3.ix.singtel.com [203.208.151
.82]
11 51 ms 51 ms 51 ms 203.208.152.194
12 49 ms 112 ms 113 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
13 112 ms 102 ms 115 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
14 97 ms 97 ms 98 ms 116.51.17.210
15 96 ms 98 ms 103 ms resolver1.opendns.com [208.67.222.222]
Why am I goint to ntt.net?
posted on November 18th, 2010 at 7:17 am
Guru
from India and it is resolving to UK servers.
|——————————————————————————————|
| WinMTR statistics |
| Host – % | Sent | Recv | Best | Avrg | Wrst | Last |
|————————————————|——|——|——|——|——|——|
| 59.92.128.1 – 0 | 3 | 3 | 31 | 62 | 78 | 78 |
| 218.248.255.82 – 0 | 3 | 3 | 62 | 72 | 78 | 78 |
| 59.163.206.157 – 0 | 3 | 3 | 62 | 67 | 78 | 62 |
| 59.163.55.245 – 0 | 3 | 3 | 46 | 62 | 78 | 63 |
| 59.163.55.245 – 0 | 3 | 3 | 46 | 62 | 78 | 46 |
| 116.0.84.41 – 0 | 3 | 3 | 62 | 73 | 94 | 63 |
| 116.0.79.13 – 0 | 3 | 3 | 46 | 67 | 109 | 47 |
| 116.0.79.26 – 0 | 3 | 3 | 93 | 124 | 187 | 187 |
| 209.58.105.70 – 0 | 3 | 2 | 203 | 241 | 280 | 280 |
| No response from host – 100 | 3 | 0 | 0 | 0 | 0 | 202 |
| 4.68.110.213 – 0 | 2 | 2 | 187 | 195 | 203 | 203 |
| 4.69.139.193 – 0 | 2 | 2 | 219 | 219 | 219 | 219 |
| 4.69.143.113 – 0 | 2 | 2 | 219 | 219 | 219 | 219 |
| 4.69.139.74 – 0 | 2 | 2 | 202 | 233 | 265 | 265 |
| 195.50.122.86 – 0 | 2 | 2 | 203 | 234 | 265 | 265 |
| 208.67.222.222 – 0 | 2 | 2 | 219 | 226 | 234 | 234 |
|________________________________________________|______|______|______|______|______|______|
posted on November 18th, 2010 at 11:08 am
John Waller
Is the new server only using 6 SAN hard drives? Whats the storage does the sever uses and needs? Just being nosy lol.
posted on November 18th, 2010 at 1:24 pm
Dhendy
Hi… I from Indonesia, here is my trace route logs :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dhendy>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms tracert 208.67.220.220
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 56 ms 61 ms 57 ms 1.subnet125-161-12.speedy.telkom.net.id [125.161
.12.1]
3 * * * Request timed out.
4 46 ms 44 ms 42 ms 74.subnet118-98-48.astinet.telkom.net.id [118.98
.48.74]
5 114 ms 111 ms 115 ms tm.net.my [58.26.87.49]
6 * * * Request timed out.
7 111 ms 111 ms 113 ms 203.131.245.157
8 124 ms 124 ms 120 ms xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net [129.250
.3.206]
9 179 ms 175 ms 173 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
10 134 ms 124 ms 127 ms 116.51.17.210
11 128 ms 131 ms 127 ms resolver2.opendns.com [208.67.220.220]
Trace complete.
Is my dns request to New Datacenter in Singapore? If not, How to make my dns request to Singapore..?
Thx
*I’m sorry, if my english bad..
posted on November 19th, 2010 at 8:46 am
Dhendy
***Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dhendy>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms tracert 208.67.220.220 (Cont)…***
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dhendy>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 78 ms 59 ms 60 ms 1.subnet125-161-12.speedy.telkom.net.id [125.161
.12.1]
3 * * * Request timed out.
4 52 ms 64 ms 58 ms 74.subnet118-98-48.astinet.telkom.net.id [118.98
.48.74]
5 129 ms 127 ms 115 ms tm.net.my [58.26.87.49]
6 * * * Request timed out.
7 114 ms 159 ms 114 ms 203.131.245.157
8 170 ms 183 ms 119 ms xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net [129.250
.3.206]
9 246 ms 180 ms 185 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
10 130 ms 131 ms 156 ms 116.51.17.210
11 129 ms 127 ms 127 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
*Sorry
posted on November 19th, 2010 at 8:49 am
sok vanthol
I am in Cambodia
I still route to USA (PAO)
Server: resolver1.opendns.com
Address: 208.67.222.222
which.opendns.com text =
“1.pao”
posted on November 19th, 2010 at 4:47 pm
Lloyd Lopez
I’m from the Philippines and using a DSL connection from Globe.
I’m not being routed to the Singapore server.
C:\Users\Lloyd>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on November 19th, 2010 at 10:46 pm
terry
on M1 fibre in singapore
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\LIN>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on November 20th, 2010 at 1:30 am
jc
from singapore (isp: singnet), and it doesn’t look good…
traceroute to resolver1.opendns.com (208.67.222.222), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.625 ms 1.297 ms 2.190 ms
2 bb116-15-49-1.singnet.com.sg (116.15.49.1) 20.863 ms 21.146 ms 22.007 ms
3 ge-3-0-0-3489.sapporo.singnet.com.sg (202.166.124.165) 19.223 ms 23.302 ms 21.841 ms
4 xe-9-0-0-3900.qt-ar04.singnet.com.sg (202.166.120.45) 21.572 ms 18.520 ms 22.217 ms
5 xe-8-3-0-0.qt-cr02.singnet.com.sg (202.166.126.209) 21.306 ms 80.304 ms 21.428 ms
6 ae6-0.singha.singnet.com.sg (202.166.120.186) 21.507 ms 20.823 ms 21.665 ms
7 ae5-0.beck.singnet.com.sg (202.166.126.41) 22.432 ms 20.143 ms 22.219 ms
8 203.208.190.57 (203.208.190.57) 21.048 ms 32.777 ms 21.598 ms
9 203.208.152.209 (203.208.152.209) 22.505 ms 23.420 ms
203.208.152.205 (203.208.152.205) 24.106 ms
10 so-3-0-1-0.hkgcw-cr3.ix.singtel.com (203.208.151.82) 54.145 ms
203.208.151.250 (203.208.151.250) 23.667 ms 22.689 ms
11 203.208.152.194 (203.208.152.194) 56.488 ms
so-3-0-0-0.hkgcw-cr4.ix.singtel.com (203.208.172.182) 53.076 ms
203.208.152.194 (203.208.152.194) 53.199 ms
12 p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 114.679 ms
203.208.152.194 (203.208.152.194) 52.943 ms
p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 111.296 ms
13 p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 114.016 ms 113.108 ms
116.51.17.210 (116.51.17.210) 114.067 ms
14 116.51.17.210 (116.51.17.210) 113.738 ms * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
posted on November 20th, 2010 at 2:14 am
Afiz
Dear David,
I’m from Malaysia, and quite shocked to find that even from Singapore ISP SingNet (as stated by LJ Phua), he only managed to get latency of 70 ms. From Malaysia is about ~75-85 ms to your Singapore resolver.
Singaporean should get sub 30ms latency to your resolver. By comparison, even from southern part of malaysia, we managed to get sub 25ms latency to our ISP DNS at Kuala Lumpur.
Maybe your team can fine tweak the BGP or anycast-routing-related config with your Singtel, your peering partner
From Malaysia with love…
64 bytes from 208.67.220.220: icmp_seq=19 ttl=59 time=77.293 ms
64 bytes from 208.67.220.220: icmp_seq=20 ttl=59 time=83.332 ms
64 bytes from 208.67.220.220: icmp_seq=21 ttl=59 time=73.515 ms
64 bytes from 208.67.220.220: icmp_seq=22 ttl=59 time=82.249 ms
64 bytes from 208.67.220.220: icmp_seq=23 ttl=59 time=74.835 ms
64 bytes from 208.67.220.220: icmp_seq=24 ttl=59 time=81.630 ms
64 bytes from 208.67.220.220: icmp_seq=25 ttl=59 time=78.180 ms
64 bytes from 208.67.220.220: icmp_seq=26 ttl=59 time=82.094 ms
64 bytes from 208.67.220.220: icmp_seq=27 ttl=59 time=77.291 ms
posted on November 20th, 2010 at 9:05 pm
tom369
i am in china
Server: resolver1.opendns.com
Address: 208.67.222.222
In China. opendns too slow. I had to use Google dns. Hope to solve this problem! !
I’m sorry my English is not good so use translation tool.
posted on November 20th, 2010 at 11:44 pm
nazrin
noiz@fatspoon:~$ traceroute 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
1 192.168.10.3 (192.168.10.3) 2.053 ms 2.015 ms 1.982 ms
2 219.93.218.176 (219.93.218.176) 5.359 ms 6.345 ms 7.784 ms
3 49.60.in-addr.arpa.tm.net.my (60.49.55.113) 6.871 ms 6.879 ms 7.002 ms
4 10.55.208.52 (10.55.208.52) 41.617 ms 41.634 ms 41.828 ms
5 203.131.245.157 (203.131.245.157) 43.156 ms 43.129 ms 43.131 ms
6 xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net (129.250.3.206) 43.124 ms 41.339 ms 41.312 ms
7 p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 104.219 ms 104.051 ms 104.022 ms
8 116.51.17.210 (116.51.17.210) 62.689 ms 62.669 ms 62.598 ms
posted on November 21st, 2010 at 6:11 pm
Shankar
Opend DNS is still routed to UK instead of Singapore
wth
how to change it so that it routes to Singapore dc rather than the UK dc?? Does my ISP play a part in this and can i tell them?? do ISP’s ever accede to customers request in this routing aspect?
1 39 ms 39 ms 39 ms 59.96.56.1
2 38 ms 38 ms 38 ms 218.248.255.2
3 44 ms 44 ms 43 ms 59.163.206.173.static.chennai.vsnl.net.in [59.16.206.173]
4 262 ms 261 ms 260 ms if-1-0-0-105.core2.CFO-Chennai.as6453.net [116.084.41]
5 260 ms 259 ms 260 ms if-15-0-0.core2.MLV-Mumbai.as6453.net [116.0.84.4]
6 258 ms 267 ms 258 ms if-13-0-0.core1.MLV-Mumbai.as6453.net [209.58.10.41]
7 * 260 ms 265 ms Vlan1816.icore1.PYE-Paris.as6453.net [209.58.105.162]
8 * * 262 ms Vlan467.icore1.PVU-Paris.as6453.net [195.219.241.69]
9 253 ms 254 ms 280 ms xe-9-1-0.edge4.paris1.level3.net [4.68.110.213]
10 278 ms 278 ms 277 ms ae-33-51.ebr1.Paris1.Level3.net [4.69.139.193]
11 257 ms 258 ms 258 ms ae-47-47.ebr1.London1.Level3.net [4.69.143.109]
12 261 ms 259 ms 261 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
13 252 ms 253 ms 254 ms 195.50.122.86
14 261 ms 261 ms 260 ms resolver1.opendns.com [208.67.222.222]
posted on November 22nd, 2010 at 7:43 am
Subhash
BSNL India service provider, looks like ends up in UK
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 24 ms 23 ms 23 ms 117.192.16.1
3 24 ms 23 ms 23 ms 218.248.160.6
4 31 ms 29 ms 29 ms 218.248.159.37
5 29 ms 30 ms 29 ms 218.248.159.37
6 29 ms 30 ms 30 ms 218.248.159.174
7 144 ms 209 ms 202 ms 59.163.206.189.static.chennai.vsnl.net.in [59.163.206.189]
8 233 ms 159 ms 245 ms 172.31.4.93
9 161 ms 144 ms 160 ms 172.31.4.93
10 691 ms * 636 ms if-1-0-0-105.core2.CFO-Chennai.as6453.net [116.0.84.41]
11 655 ms 612 ms 613 ms if-15-1-0.core1.CFO-Chennai.as6453.net [116.0.79.13]
12 632 ms 667 ms 574 ms if-2-0-0.core1.MLV-Mumbai.as6453.net [116.0.79.26]
13 557 ms 561 ms 568 ms Vlan1124.icore1.PYE-Paris.as6453.net [209.58.105.70]
14 560 ms 557 ms * Vlan467.icore1.PVU-Paris.as6453.net [195.219.241.69]
15 609 ms 612 ms 612 ms xe-9-1-0.edge4.paris1.level3.net [4.68.110.213]
16 323 ms 407 ms 408 ms ae-33-51.ebr1.Paris1.Level3.net [4.69.139.193]
17 631 ms 612 ms 612 ms ae-46-46.ebr1.London1.Level3.net [4.69.143.105]
18 630 ms 612 ms * ae-1-51.edge4.London1.Level3.net [4.69.139.74]
19 608 ms 612 ms 612 ms 195.50.122.86
20 630 ms 613 ms 611 ms resolver1.opendns.com [208.67.222.222]
posted on November 22nd, 2010 at 8:53 am
Marco van den Berg
(Enterprise) user from the Philippines: still routed to Seattle by local ISP (PLDT).
Marco
posted on November 22nd, 2010 at 5:58 pm
Justin Lee
Nice work!
Traceroute from here (M1 Corporate Broadband, Singapore) seems to go to PCCW Singapore and stops there.
I deleted the first two hops containing my IP for security reasons:
traceroute to 208.67.220.220 (208.67.220.220), 64 hops max, 52 byte packets
3 10.253.232.190 (10.253.232.190) 50.302 ms 30.980 ms 64.041 ms
4 ge-0-2.megapop01.qala.com.sg (210.193.4.62) 124.157 ms 295.427 ms 247.741 ms
5 ge-0-2.alpha035.qala.com.sg (210.193.4.61) 58.983 ms 27.584 ms 63.103 ms
6 ge-csw-v21.alpha020.qala.com.sg (203.211.159.60) 72.942 ms 47.914 ms 23.812 ms
7 ge-0-1.alpha002.qala.com.sg (203.211.159.2) 147.566 ms 30.530 ms 28.228 ms
8 fe3-3.br01.sin02.pccwbtn.net (63.218.165.37) 31.084 ms 27.054 ms 64.701 ms
posted on November 23rd, 2010 at 10:41 pm
Anton
C:\Windows\system32>tracert 208.67.220.220
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1
posted on November 24th, 2010 at 2:41 am
Augustine
Hi I am Augustine from Singapore.
Here is my traceroute from my office to 208.67.222.222.
My traceroute result still shows that it still goes to SanJose instead of Singapore
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.12.1.250
2
posted on November 24th, 2010 at 2:48 am
vanthol
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 192.168.8.1
2 25 ms 21 ms 7 ms 111.118.158.45
3 * * * Request timed out.
4 6 ms 5 ms 5 ms 117.120.24.181
5 6 ms 5 ms 5 ms 117.120.24.189
6 41 ms 10 ms 10 ms 203.113.185.253
7 53 ms 54 ms 52 ms 203.131.243.93
8 228 ms 231 ms 226 ms ae-0.r20.newthk01.hk.bb.gin.ntt.net [203.131.240.241]
9 * * * Request timed out.
10 295 ms 262 ms 264 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.250.6.97]
11 99 ms 101 ms 99 ms 116.51.17.210
12 99 ms 106 ms 100 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
posted on November 24th, 2010 at 3:02 am
netahoy
Thanks for the new server!
On Sify enterprise network… and landing to Singapore
..but then wonder why does it go from Singtet to NTT Japan?
Hop Hostname IP Time 1 Time 2
1 HIDEME 0.123ms pmtu
1 HIDEME 1.995ms *
1 HIDEME 2.901ms *
2 segment-HIDEME.sify.net 8.919ms *
3 no reply *
4 no reply *
5 no reply *
6 no reply *
7 segment-HIDEME.sify.net 66.607ms *
8 segment-HIDEME.sify.net 54.685ms asymm
9 lan-202-144-74-118.sify.net 88.727ms asymm
10 segment-119-227.sify.net 90.290ms asymm
11 segment-119-227.sify.net 88.316ms asymm
12 203.208.174.85 89.888ms asymm
13 203.208.152.233 94.900ms asymm
14 203.208.151.249 90.118ms asymm
15 so-3-0-1-0.hkgcw-cr3.ix.singtel.com 118.171ms asymm
16 203.208.152.194 135.876ms asymm
17 p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net 189.661ms asymm
18 116.51.17.210 167.058ms asymm
19 no reply *
20 no reply *
… truncated
30 no reply *
31 no reply *
posted on November 24th, 2010 at 3:27 am
installster
Singapore, Singtel:
$ tcptraceroute.exe resolver2.opendns.com:53
Tracing route to 208.67.220.220 [resolver2.opendns.com] on port 53
Over a maximum of 30 hops.
1 2 ms 2 ms 2 ms 192.168.2.1
2 3 ms 3 ms 3 ms 192.168.1.254
3 12 ms 10 ms 12 ms 116.14.108.1 [bb116-14-108-1.singnet.com.sg]
4 12 ms 12 ms 12 ms 202.166.122.81 [te3-0-1-3450.sake.singnet.com.sg]
5 12 ms 10 ms 12 ms 202.166.121.129 [xe-0-0-0-3000.qt-ar04.singnet.com.sg]
6 14 ms 12 ms 10 ms 202.166.126.209 [xe-8-3-0-0.qt-cr02.singnet.com.sg]
7 10 ms 12 ms 12 ms 202.166.120.186 [ae6-0.singha.singnet.com.sg]
8 14 ms 12 ms 12 ms 202.166.126.41 [ae5-0.beck.singnet.com.sg]
9 22 ms 12 ms 14 ms 203.208.190.129
10 13 ms 13 ms 9 ms 203.208.152.221
11 41 ms 41 ms 41 ms 203.208.172.182 [so-3-0-0-0.hkgcw-cr4.ix.singtel.com]
12 43 ms 43 ms 43 ms 203.208.152.194
13 106 ms 104 ms 106 ms 129.250.6.97 [p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net]
14 106 ms 106 ms 106 ms 116.51.17.210
15 Destination Reached in 106 ms. Connection established to 208.67.220.220
Trace Complete.
posted on November 28th, 2010 at 12:39 am
Jasin Natael
Hi! Here’s my traceroute result. I’m in the Philippines. Looks like i’m not talking to SG:
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 60 ms 61 ms 60 ms 112.198.205.1
3 61 ms 61 ms 61 ms 222.127.228.57
4 60 ms 59 ms 61 ms 120.28.1.37
5 90 ms 91 ms 91 ms 120.28.0.37
6 241 ms 241 ms 240 ms 120.28.0.82
7 266 ms 266 ms 263 ms 4.79.42.165
8 266 ms 265 ms 265 ms ae-21-69.car1.SanJose2.Level3.net [4.68.18.11]
9 251 ms 252 ms 250 ms SPLICE-COMM.car1.SanJose2.Level3.net [4.59.0.174
]
10 251 ms 251 ms 251 ms resolver1.opendns.com [208.67.222.222]
posted on November 28th, 2010 at 8:56 am
Keith C
Hi, I’m from Hong Kong, it still route to US.
7 178 ms 181 ms 180 ms ae-0.r20.plalca01.us.bb.gin.ntt.net [129.250.4.118]
8 180 ms 178 ms 203 ms po-2.r04.plalca01.us.bb.gin.ntt.net [129.250.3.2
38]
9 169 ms 166 ms 168 ms ge-2-3.r04.plalca01.us.ce.gin.ntt.net [140.174.2
1.166]
10 173 ms 169 ms 170 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
posted on November 30th, 2010 at 9:13 am
Ken
Seems like there isn’t any updates from the numerous reports people are posting about not routing to the correct DNS. Is this the kind of service OpenDNS is providing to end-users?
Even a simple update post would be useful rather than keeping us wondering what’s going on; we know that this is no perfect science
posted on December 1st, 2010 at 8:32 am
Laura Oppenheimer
Hi Ken,
We are looking at comments as they come in (and reports in our Support center) and using that info to make the changes necessary to those who should be routed to our Singapore datacenter should be.
In general, dropping a note to our support team is a better outlet for getting one on one support and delving a little further into an issue.
If there’s something specific you’d like us to take a look at, let us know there!
-Laura
posted on December 1st, 2010 at 12:13 pm
Jitesh Ghushe
Almost all OpenDNS users of BSNL and other ISP are getting routed to NON singapore location. Can you please look into this.
posted on December 2nd, 2010 at 3:02 am
You
Shanghai,China
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 26 ms 31 ms 31 ms 116.235.8.1
2 15 ms 15 ms 15 ms 124.74.20.113
3 15 ms 15 ms 15 ms 124.74.209.65
4 15 ms 15 ms 15 ms 61.152.86.50
5 15 ms 15 ms 15 ms 202.97.33.30
6 15 ms 15 ms 15 ms 202.97.33.102
7 15 ms * * 202.97.60.10
8 * 77 ms 77 ms p16-7-3-2.r23.tokyjp01.jp.bb.gin.ntt.net [61.1
.146.141]
9 156 ms * 156 ms as-1.r03.sngpsi02.sg.bb.gin.ntt.net [129.250.6
21]
10 * 156 ms 156 ms xe-4-0-0.r02.sngpsi02.sg.bb.gin.ntt.net [129.2
.4.23]
11 155 ms * * 116.51.17.210
12 * * 144 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
posted on December 4th, 2010 at 8:16 pm
Binod
From Bangalare, India…
binod-pgs-macbook:~ binod$ traceroute 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 1.795 ms 1.589 ms 1.395 ms
2 59.99.98.1 (59.99.98.1) 22.330 ms 21.850 ms 26.089 ms
3 218.248.255.66 (218.248.255.66) 21.353 ms 20.838 ms 21.298 ms
4 59.163.206.173.static.chennai.vsnl.net.in (59.163.206.173) 36.822 ms 37.261 ms 37.976 ms
5 if-1-0-0-105.core2.CFO-Chennai.as6453.net (116.0.84.41) 245.434 ms 246.514 ms 245.067 ms
6 if-6-1-0.core2.MLV-Mumbai.as6453.net (116.0.84.54) 267.935 ms 268.137 ms 267.826 ms
7 if-13-0-0.core1.MLV-Mumbai.as6453.net (209.58.105.41) 269.860 ms 270.218 ms 269.443 ms
8 if-14-0-0.core1.PYE-Paris.as6453.net (209.58.105.110) 358.120 ms 1081.619 ms 474.949 ms
9 Vlan167.icore1.PYE-Paris.as6453.net (80.231.196.10) 282.868 ms 273.076 ms 270.289 ms
10 * * *
11 xe-9-1-0.edge4.paris1.level3.net (4.68.110.213) 388.981 ms 385.694 ms 387.020 ms
12 ae-33-51.ebr1.Paris1.Level3.net (4.69.139.193) 296.390 ms 297.349 ms 298.804 ms
13 ae-48-48.ebr1.London1.Level3.net (4.69.143.113) 388.740 ms 390.432 ms ae-47-47.ebr1.London1.Level3.net (4.69.143.109) 274.955 ms
14 ae-1-51.edge4.London1.Level3.net (4.69.139.74) 275.687 ms 275.661 ms 277.579 ms
15 195.50.122.86 (195.50.122.86) 307.008 ms 314.531 ms 311.819 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 *traceroute: sendto: No route to host
traceroute: wrote 208.67.222.222 40 chars, ret=-1
* 192.168.2.1 (192.168.2.1) 1.216 ms !N
31 * * *
32 *
posted on December 6th, 2010 at 5:01 am
Javed Khan
Dear OpenDNS, my traffic is still being routed through amsterdam instead of your singapore datacenter. I’m located in lahore, pakistan. Please assist.
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 50 ms 61 ms 53 ms 119.152.10.1
3 45 ms 44 ms 45 ms 203.99.170.198
4 48 ms 44 ms 44 ms 221.120.252.9
5 63 ms 63 ms 65 ms 221.120.254.18
6 68 ms 69 ms 69 ms static-khidr-ni01-sw.pie.net.pk [202.125.128.141
]
7 177 ms 180 ms 179 ms po4-0-2.ccr01.mrs01.atlas.cogentco.com [149.6.15
4.89]
8 185 ms 184 ms 183 ms te0-2-0-6.ccr21.mrs01.atlas.cogentco.com [154.54
.38.149]
9 189 ms 188 ms 189 ms te0-1-0-3.ccr21.par01.atlas.cogentco.com [130.11
7.2.214]
10 367 ms 202 ms 212 ms te2-1.ccr02.par04.atlas.cogentco.com [130.117.1.
254]
11 190 ms 189 ms 190 ms verio.par04.atlas.cogentco.com [130.117.15.42]
12 190 ms 190 ms 189 ms xe-5-1-0.r21.parsfr01.fr.bb.gin.ntt.net [129.250
.2.42]
13 200 ms 200 ms 198 ms p64-3-0-0.r22.amstnl02.nl.bb.gin.ntt.net [129.25
0.4.16]
14 * 200 ms * po-1.r01.amstnl02.nl.bb.gin.ntt.net [129.250.4.7
1]
15 198 ms 198 ms 200 ms opendns-0.r01.amstnl02.nl.bb.gin.ntt.net [81.20.
64.82]
16 198 ms 200 ms 198 ms resolver1.opendns.com [208.67.222.222]
posted on December 6th, 2010 at 5:53 pm
Jeffrez Kz - (CAMBODIA)
Hi There!
Here in Phnom Penh, Cambodia. The result comes not so bad, I guess there are correct routing here.
Anyway, compare to Google PUBLIC DNS (37ms), OPENDNS (117ms) Still far behind in here which is about 3 times higher.
With that latency it is quite acceptable, however it would be much better if it can drop down a bit more.
=========== OPEN DNS RESULT ==========================
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 3 ms 1 ms 2 ms 10.82.248.134
2 3 ms 2 ms 1 ms 10.82.248.134
3 2 ms 2 ms 2 ms 10.82.248.133
4 2 ms 2 ms 2 ms eze-119.82.248.233.ezecom.com.kh [119.82.248.233
]
5 53 ms 54 ms 53 ms 203.131.245.181
6 54 ms 60 ms 55 ms po-1.r00.newthk02.hk.bb.gin.ntt.net [203.131.244
.14]
7 54 ms 54 ms 56 ms xe-1-3-0.r20.newthk02.hk.bb.gin.ntt.net [129.250
.3.100]
8 118 ms 118 ms 118 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
9 118 ms 119 ms 138 ms 116.51.17.210
10 117 ms 118 ms 118 ms resolver1.opendns.com [208.67.222.222]
///////////////////
Tracing route to resolver2.opendns.com [208.67.220.220]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 10.82.248.134
2 2 ms 1 ms 2 ms 10.82.248.134
3 1 ms 2 ms 2 ms 10.82.248.133
4 2 ms 3 ms 2 ms eze-119.82.248.229.ezecom.com.kh [119.82.248.229
]
5 54 ms 54 ms 55 ms 203.131.245.181
6 54 ms 54 ms 54 ms po-1.r00.newthk02.hk.bb.gin.ntt.net [203.131.244
.14]
7 54 ms 54 ms 54 ms xe-1-3-0.r20.newthk02.hk.bb.gin.ntt.net [129.250
.3.100]
8 118 ms 119 ms 118 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
9 118 ms 118 ms 118 ms 116.51.17.210
10 118 ms 117 ms 118 ms resolver2.opendns.com [208.67.220.220]
Trace complete.
======== GOOGLE PUBLIC DNS RESULT ======================
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 10.82.248.134
2 2 ms 2 ms 2 ms 10.82.248.134
3 3 ms 1 ms 3 ms 10.82.248.133
4 3 ms 2 ms 1 ms eze-119.82.248.229.ezecom.com.kh [119.82.248.229
]
5 34 ms 33 ms 34 ms d1-93-230-143-118-on-nets.com [118.143.230.93]
6 35 ms 34 ms 35 ms 218.189.97.97
7 36 ms 35 ms 35 ms peer.hgc.com.hk [218.189.96.138]
8 36 ms 35 ms 36 ms 209.85.241.58
9 36 ms 35 ms 36 ms 209.85.253.71
10 44 ms 35 ms 37 ms 216.239.48.230
11 37 ms 35 ms 37 ms google-public-dns-a.google.com [8.8.8.8]
Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 10.82.248.134
2 3 ms 2 ms 2 ms 10.82.248.134
3 3 ms 2 ms 2 ms 10.82.248.133
4 2 ms 3 ms 4 ms eze-119.82.248.229.ezecom.com.kh [119.82.248.229
]
5 34 ms 33 ms 34 ms d1-93-230-143-118-on-nets.com [118.143.230.93]
6 132 ms 205 ms 165 ms 218.189.97.97
7 35 ms 38 ms 37 ms peer.hgc.com.hk [218.189.96.158]
8 123 ms 34 ms 36 ms 209.85.241.56
9 37 ms 36 ms 35 ms 216.239.43.19
10 40 ms 36 ms 39 ms 216.239.48.234
11 37 ms 37 ms 36 ms google-public-dns-b.google.com [8.8.4.4]
Trace complete.
posted on December 9th, 2010 at 11:32 am
Sanan K.
*** From Bangkok Thailand ***
C:\>tracert -d 208.67.222.222
Tracing route to 208.67.222.222 over a maximum of 30 hops
1 35 ms 34 ms 34 ms 203.150.217.129
2 36 ms 34 ms 34 ms 203.150.217.254
3 35 ms 34 ms 35 ms 203.150.222.9
4 35 ms 33 ms 34 ms 61.19.10.9
5 35 ms 43 ms 33 ms 61.19.9.133
6 34 ms 35 ms 33 ms 61.19.9.38
7 84 ms 83 ms 90 ms 61.19.9.110
8 87 ms 82 ms 84 ms 203.131.245.25
9 86 ms 84 ms 84 ms 129.250.3.206
10 192 ms 147 ms 150 ms 129.250.6.97
11 149 ms 176 ms 147 ms 116.51.17.210
12 150 ms 148 ms 149 ms 208.67.222.222
Trace complete.
posted on December 10th, 2010 at 4:28 pm
Mistri
208.67.222.222 and 220.220 still resolve to UK and not to Singapore in BSNL India. Is this routing totally controlled by ISP? Can OpenDNS do something to route it to Singapore.
Tracing route to 208.67.222.222 over a maximum of 30 hops
1 39 ms 39 ms 39 ms 59.92.128.1
2 67 ms 67 ms 66 ms 218.248.255.90
3 79 ms 78 ms 80 ms 121.244.68.77
4 184 ms 183 ms 183 ms 209.58.105.153
5 212 ms 196 ms 837 ms 195.219.195.181
6 189 ms 181 ms 194 ms 80.231.196.1
7 * 193 ms * 195.219.241.69
8 183 ms 183 ms 182 ms 4.68.110.213
9 183 ms 184 ms 183 ms 4.69.139.193
10 192 ms 182 ms 191 ms 4.69.143.105
11 182 ms 182 ms 182 ms 4.69.139.74
12 184 ms 182 ms 181 ms 195.50.122.86
13 181 ms 181 ms 181 ms 208.67.222.222
posted on December 11th, 2010 at 11:28 am
Marco Tulio
Dear OpenDNS…
why there are more plans for deployment of OpenDNS in Brazil?
Thank you for attention.
posted on December 14th, 2010 at 4:02 am
muneer
i am muneer from india. in india it not getting singappur datacenter.
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 117.204.80.1
3 11 ms 9 ms 9 ms 218.248.173.58
4 30 ms 28 ms 28 ms 59.163.206.189.static.chennai.vsnl.net.in [59.16
3.206.189]
5 58 ms 56 ms 56 ms 59.163.55.245.static.vsnl.net.in [59.163.55.245]
6 58 ms 57 ms 56 ms 59.163.55.245.static.vsnl.net.in [59.163.55.245]
7 58 ms 57 ms 57 ms if-1-0-0-105.core2.CFO-Chennai.as6453.net [116.0
.84.41]
8 92 ms 89 ms 89 ms if-1-0-1.core1.MLV-Mumbai.as6453.net [116.0.84.1
8]
9 200 ms 197 ms 202 ms if-9-1-0-0.tcore1.PYE-Paris.as6453.net [209.58.1
05.110]
10 * * * Request timed out.
11 * 204 ms * Vlan13.icore1.PVU-Paris.as6453.net [80.231.153.6
]
12 * 514 ms 307 ms xe-9-1-0.edge4.paris1.level3.net [4.68.110.213]
13 433 ms 304 ms 411 ms ae-33-51.ebr1.Paris1.Level3.net [4.69.139.193]
14 433 ms 303 ms 413 ms ae-45-45.ebr1.London1.Level3.net [4.69.143.101]
15 2278 ms 304 ms 414 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
16 437 ms 308 ms 510 ms 195.50.122.86
17 432 ms 302 ms 413 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
posted on December 25th, 2010 at 9:18 am
Joseph
after all these month, starhub a singapore isp is still not routing to the singapore opendns data centre.
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on January 1st, 2011 at 7:29 pm
Adrian
Hi I’m from Singapore, my traffic is still being routed through USA.
Last login: Mon Jan 3 17:06:58 on console
adrian-macbook:~ adrian$ traceroute 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 3.257 ms 4.155 ms 4.582 ms
2 * * cm1.omega48.maxonline.com.sg (218.186.48.1) 10.194 ms
3 172.20.26.1 (172.20.26.1) 10.885 ms 14.475 ms 7.735 ms
4 172.26.26.1 (172.26.26.1) 9.419 ms 12.151 ms 12.726 ms
5 172.20.7.26 (172.20.7.26) 19.482 ms 27.853 ms 10.996 ms
6 172.20.7.70 (172.20.7.70) 23.264 ms 14.666 ms 11.190 ms
7 203.116.17.65 (203.116.17.65) 17.120 ms 16.317 ms 15.010 ms
8 203.118.3.226 (203.118.3.226) 13.817 ms 20.796 ms 12.162 ms
9 so-7-0-1.edge6.sanjose1.level3.net (4.53.22.1) 218.442 ms 221.066 ms 225.285 ms
10 ae-31-99.car1.sanjose2.level3.net (4.68.18.203) 229.280 ms
ae-41-89.car1.sanjose2.level3.net (4.68.18.139) 216.582 ms
ae-31-99.car1.sanjose2.level3.net (4.68.18.203) 215.945 ms
11 splice-comm.car1.sanjose2.level3.net (4.59.0.174) 431.928 ms 299.606 ms 251.599 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
posted on January 3rd, 2011 at 2:24 am
adikus
Hi Admin,
I’m from Dumai – Indonesia
But my traffic is still being routed through SanJose – USA.
Please help me.
#traceroute 208.67.222.222 [root @ hostname]
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 40 byte packets
1 (123.231.242.105) 3.187 ms 4.219 ms 4.691 ms
2 (202.152.44.245) 21.823 ms 9.426 ms 5.758 ms
3 (202.152.44.246) 10.221 ms 21.884 ms 6.581 ms
4 (202.152.2.65) 53.114 ms 52.572 ms 59.315 ms
5 jktidsigr2-giga-0-1.jkt.idola.net.id (202.152.0.164) 37.865 ms 52.460 ms 37.821 ms
6 SINEQNIGR1.idola.net.id (202.152.0.51) 88.674 ms 70.189 ms 62.774 ms
7 Vlan555.icore1.SVQ-Singapore.as6453.net (120.29.215.49) 75.630 ms 96.859 ms 71.887 ms
8 * * *
9 * Vlan1104.icore1.SQN-SanJose.as6453.net (209.58.116.9) 246.316 ms 249.288 ms
10 ix-10-0.icore1.SQN-SanJose.as6453.net (209.58.116.14) 302.563 ms 325.330 ms 247.762 ms
11 ae-31-99.car1.SanJose2.Level3.net (4.68.18.203) 249.201 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75) 249.158 ms ae-21-69.car1.SanJose2.Level3.net (4.68.18.11) 247.685 ms
12 SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174) 258.227 ms 256.166 ms 265.393 ms
13 * * *
14 * * *
15 * * *
posted on January 3rd, 2011 at 10:00 pm
Mike
My traceroute from Sydney, Australia. Ignore the timings – I just got shaped by my ISP
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on January 6th, 2011 at 4:29 am
iron2000
Just switched back to OpenDNS to try out but it seems like I am being not directed to the Singapore site:
1
posted on January 6th, 2011 at 9:42 pm
KHALID HARIS
HELLO,
WISHING ALL A HAPPY NEW YEAR OVER THERE.
I’m Dr. KK Haris from Raipur, Chhattisgarh, INDIA. My trace route shows I’m still not routed through the Singapore Data centre. My family shield is also not working for Linksys router. I’ve the OpenDNS Updater installed for windows, as I’ve a dynamic IP, and it is updating the IP promptly.
Trace route -
C:\Users\KK HARIS>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 2 ms 1 ms
posted on January 7th, 2011 at 7:40 pm
KHALID HARIS
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\KK HARIS>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 2 ms 1 ms Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\KK HARIS>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 2 ms 1 ms
posted on January 7th, 2011 at 7:42 pm
Khalid Haris
Can’t find the Singapore Data center.
C:\WINDOWS\SYSTEM32>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 1 ms
posted on January 8th, 2011 at 7:54 am
Ebuks
Dear OpenDNS,
I recently heard about OpenDNS through a colleague and I was excited about trying it out. I intended using it for website filtering. Protect the children from getting into certain websites they shouldn’t be going to.
I planned on configuring the DNS IP address on a home router later. However, to test out the service, I co figured the following IP Address as my primary and secondary DNS servers 208.67.222.222 and 208.67.220.220. I visited certain (x rated) websites which I though would be blocked by this service but to my surprise, it opened! I guess my question is what you guy meant by ‘web filtering’?
How do I get this to work? Is there an alternate DNS IP address I can use?
-Ebuks
posted on January 11th, 2011 at 10:05 am
tigerpiceks
This one from Smart Telecom (EVDO) Indonesia.
C:\Users\duke>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 * 1284 ms 106 ms 10.20.30.45
2 * * * Request timed out.
3 * * * Request timed out.
4 112 ms 103 ms 98 ms 10.28.11.34
5 * * * Request timed out.
6 105 ms 106 ms 302 ms 10.17.97.40
7 * 128 ms 96 ms 202.70.48.49
8 108 ms 106 ms 106 ms 202.70.48.17
9 * * 116 ms 202.43.179.41
10 * * * Request timed out.
11 331 ms 395 ms 311 ms 202.43.176.222
12 125 ms 127 ms 134 ms 203.208.131.101
13 735 ms 456 ms 145 ms ge-1-1-2-0.sngtp-dr2.ix.singtel.com [203.208.152
.58]
14 177 ms 177 ms 185 ms 203.208.152.213
15 222 ms 156 ms 131 ms 203.208.151.250
16 169 ms 171 ms 181 ms so-3-0-0-0.hkgcw-cr4.ix.singtel.com [203.208.172
.182]
17 273 ms 177 ms 165 ms 203.208.152.194
18 220 ms 239 ms 223 ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
19 174 ms 193 ms 190 ms 116.51.17.210
20 196 ms 200 ms 188 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
posted on January 11th, 2011 at 8:49 pm
Laura Oppenheimer
Hi Ebuks,
Thanks for dropping us a note about your issue!
Simply switching to OpenDNS for your DNS does NOT protect you from the x-rated stuff out there. In order to get Web content filtering set up, you’ll need to sign into the dashboard, set up your network, and choose which categories of content you’d like to block.
The reason is that in order to do Web content filtering, we need to know your IP address so we can apply your settings.
If you have further questions about this, drop us a note in our support center — we can take a look: https://www.opendns.com/dashboard/support/
Thanks,
Laura
posted on January 12th, 2011 at 10:17 am
Ruel Montero
Dear OPENDNS,
208.67.222.222 is from United States(US) in region North America
TraceRoute to 208.67.222.222 [resolver1.opendns.com]
Hop (ms) (ms) (ms) IP Address Host name
1 14 17 7 72.249.0.65 -
2 15 19 10 206.123.64.21 -
3 7 8 6 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
4 8 9 6 4.69.145.69 ae-23-70.car3.dallas1.level3.net
5 13 14 25 4.71.120.66 splice-comm.car3.dallas1.level3.net
6 15 12 7 208.67.222.222 resolver1.opendns.com
Trace complete
My IP
121.97.116.34 is from Philippines(PH) in region Southern and Eastern Asia
TraceRoute to 121.97.116.34 [121.97.116.34.bti.net.ph]
Hop (ms) (ms) (ms) IP Address Host name
1 176 5 229 72.249.128.5 -
2 11 12 7 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 8 13 6 4.69.145.197 ae-43-90.car3.dallas1.level3.net
4 13 32 12 4.68.63.194 -
5 45 43 46 213.248.80.13 las-bb1-link.telia.net
6 56 54 59 80.91.247.171 sjo-bb1-link.telia.net
7 282 271 286 213.248.98.242 bayan-ic-124584-sjo-bb1.c.telia.net
8 272 266 252 202.78.119.10 -
9 278 271 275 121.96.0.1 121.96.0.1.bti.net.ph
10 308 296 305 121.97.116.34 121.97.116.34.bti.net.ph
Trace complete
Thanks
posted on January 12th, 2011 at 10:44 pm
rizal
.. I’am from indonesia .. my trace still got San Jose Server as resolver ..
posted on January 20th, 2011 at 2:00 am
Simon
- Going to SanJose, from Sydney Australia
$ traceroute -U 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0.314 ms 0.332 ms 0.356 ms
2 10.236.48.1 (10.236.48.1) 17.774 ms 19.553 ms 19.734 ms
3 vl400.kacz-s-1.ken.bigpond.net.au (58.160.12.1) 19.867 ms 20.004 ms 20.440 ms
4 te6-2.agg2.ken.bigpond.net.au (58.160.15.246) 20.127 ms 20.298 ms 20.855 ms
5 172.18.239.38 (172.18.239.38) 20.241 ms 20.523 ms 20.660 ms
6 172.18.239.33 (172.18.239.33) 20.851 ms 8.802 ms 7.978 ms
7 Bundle-Ether11.chw48.Sydney.telstra.net (203.45.17.21) 11.513 ms 18.428 ms 18.561 ms
8 Bundle-Ether6.chw-core2.Sydney.telstra.net (203.50.6.153) 19.142 ms 19.278 ms 19.298 ms
9 Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90) 24.057 ms 23.906 ms 24.285 ms
10 TenGigabitEthernet6-0.sydo-core01.Sydney.reach.com (203.50.13.38) 17.770 ms 17.991 ms 18.105 ms
11 i-10-0-0.syd-core03.bi.reach.com (202.84.221.85) 18.542 ms 18.676 ms 18.783 ms
12 i-12-2-0.sjc-core01.bx.reach.com (202.84.140.157) 175.759 ms 176.076 ms 172.576 ms
13 i-2-1.eqnx02.bi.reach.com (202.84.251.122) 178.338 ms 177.970 ms 178.181 ms
14 l3-peer.eqnx02.pr.reach.com (134.159.62.198) 207.217 ms 207.158 ms 207.160 ms
15 ae-21-69.car1.SanJose2.Level3.net (4.68.18.11) 186.873 ms ae-31-99.car1.SanJose2.Level3.net (4.68.18.203) 183.430 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75) 183.740 ms
16 SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174) 372.320 ms 369.668 ms 368.502 ms
17 resolver1.opendns.com (208.67.222.222) 179.333 ms 202.413 ms 198.676 ms
posted on January 29th, 2011 at 4:17 am
Koole
and this the result from FirstMedia Indonesia;
traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.562 ms 1.019 ms 0.744 ms
2 10.9.0.1 (10.9.0.1) 13.259 ms 9.378 ms 10.492 ms
3 192.168.190.229 (192.168.190.229) 10.382 ms 9.582 ms 11.521 ms
4 192.168.190.145 (192.168.190.145) 39.608 ms 33.866 ms 8.089 ms
5 fm-ip-202.73.96.6.fast.net.id (202.73.96.6) 8.201 ms 8.455 ms 7.746 ms
6 fm-ip-202.73.96.5.fast.net.id (202.73.96.5) 8.153 ms 10.122 ms 7.811 ms
7 fm-ip-202.73.96.9.fast.net.id (202.73.96.9) 19.482 ms 14.124 ms 8.936 ms
8 ip-125-33.mcs.napinfo.net (119.110.125.33) 23.618 ms 18.491 ms 9.931 ms
9 ip-112-226.mcs.napinfo.net (119.110.112.226) 19.754 ms 19.890 ms 22.181 ms
10 vlan558.icore1.svw-singapore.as6453.net (116.0.71.113) 35.916 ms 37.741 ms 34.259 ms
11 if-0-1712.tcore2.svw-singapore.as6453.net (180.87.15.21) 23.476 ms 22.413 ms 22.214 ms
12 if-11-2.tcore1.lvw-losangeles.as6453.net (180.87.15.150) 193.968 ms 192.456 ms 192.516 ms
13 if-10-0-0-12.mcore3.laa-losangeles.as6453.net (66.110.59.54) 191.393 ms 206.862 ms 194.674 ms
14 0.so-1-0-0.br2.lax7.alter.net (204.255.169.89) 192.746 ms 203.536 ms 191.822 ms
15 0.so-2-2-0.xt1.lax7.alter.net (152.63.112.146) 194.341 ms 193.186 ms 196.045 ms
16 0.so-7-1-0.xl3.lax15.alter.net (152.63.1.226) 201.757 ms 200.652 ms 202.657 ms
17 tengige0-4-2-0.gw4.lax15.alter.net (152.63.115.186) 199.944 ms
tengige0-4-1-0.gw4.lax15.alter.net (152.63.115.178) 200.803 ms 200.255 ms
18 65.204.147.2 (65.204.147.2) 206.096 ms 200.076 ms 200.474 ms
19 * * *
20 * * *
21 * * *
22 * * *
posted on March 12th, 2011 at 4:44 pm
Peter
Tracert is still going to San Jose:
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
1 192.168.0.254 (192.168.0.254) 0.557 ms 0.743 ms 0.816 ms
2 * * *
3 242.246.65.202.unknown.m1.com.sg (202.65.246.242) 38.280 ms 38.219 ms 38.206 ms
4 241.246.65.202.unknown.m1.com.sg (202.65.246.241) 7.535 ms 7.527 ms 7.366 ms
5 Gi2-1.gw2.sin1.asianetcom.net (203.192.154.17) 8.421 ms 8.363 ms 9.112 ms
6 gi10-0.gw5.sin1.asianetcom.net (202.147.48.86) 9.177 ms 7.282 ms 8.353 ms
7 te0-0-2-0.wr2.sin0.asianetcom.net (61.14.157.113) 9.415 ms 9.448 ms 9.392 ms
8 te0-0-2-0.wr2.osa0.asianetcom.net (61.14.157.62) 183.927 ms 183.882 ms 183.798 ms
9 te0-0-4-0.wr1.osa0.asianetcom.net (61.14.157.21) 183.394 ms 184.506 ms 184.442 ms
10 61-14-157-98.asianetcom.net (61.14.157.98) 188.250 ms 188.203 ms 184.489 ms
11 xe-7-3-0.edge2.SanJose3.Level3.net (4.53.210.29) 188.231 ms 189.061 ms 189.752 ms
12 ae-31-90.car1.SanJose2.Level3.net (4.69.152.203) 186.415 ms ae-41-80.car1.SanJose2.Level3.net (4.69.152.139) 187.416 ms ae-11-70.car1.SanJose2.Level3.net (4.69.152.75) 192.915 ms
13 SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174) 193.056 ms 192.868 ms 193.261 ms
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=4 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=5 ttl=50 time=186 ms
posted on April 12th, 2011 at 7:20 pm
rioven
My result from Malaysia (TM Streamyx)
Tracing route to resolver1.opendns.com [208.67.222.222] with TTL of 32:
1 0ms 0ms 0ms 192.168.2.1
2 * 7ms 7ms 219.93.218.177
3 92ms 107ms 7ms 219.93.219.29
4 50ms 48ms 49ms 10.55.208.52
5 212ms 215ms 293ms 203.131.245.157
6 207ms 270ms 249ms xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net [129.250.3.206]
7 253ms 257ms 255ms p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.250.6.97]
8 94ms 78ms 95ms 116.51.17.210
9 137ms 74ms 72ms resolver1.opendns.com [208.67.222.222]
Traceroute complete.
posted on April 20th, 2011 at 11:39 am
Jason Tan
My ISP is starhub. Why is the traffic routed to usa before coming to the sg opendns server?
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1
posted on April 23rd, 2011 at 9:09 pm