awesome !

Wow! At last! Welcome to Singapore! (OK, I'm actually from Malaysia, which is only a bridge away from Singapore)

"Our formula for picking locations is simple: the more traffic we get from a particular region, the more likely it is we'll put a data center there." <-- Yeah!

Cloudflare needs to now launch more East Coast connectivity because that is one of the places that has poor response times according to Yottaa.com

">

that's superb!

@benjamin I wouldn't necessarily trust Yottaa's numbers. We're within 30ms of 99% of the east coast of the US and in the two biggest IBXs there: NYC & ASH.

@Matthew What could be causing Yottaa's response time & load time data to be inaccurate? My understanding is they have a network of servers that do pulls of content from each major geolocation and also do pings and traceroutes. Have you done any sampling using their service and compared results on say a site using Cloudflare versus one that is not? If Yottaa's data is not trustworthy do you have any suggestions for a more accurate independent testing tool?

This is great news for Aussies. Hopefully more will join now. If you ever need a centre in Australia at a future date http://www.pipenetworks.com/ might be able to point you in the right direction.

Mmm, any IP to test ping and tracing? I'm from Indonesia, just some miles from Singapore.

@bledaone - run a traceroute to your site on CloudFlare and see what the results report. Don't pay attention to the IP... we anycast, so the same IPs are used worldwide. But the traceroute will give hints as to location. If you're not being directed to our Singapore node, we'll see what we can do about tuning the routing.

@bledaone just do tracert yoursite.com is DOS. My site is still going to the USA.

@John Robert I am in Australia I thought it would be quicker going to Singapore for me in Australia. Does it take the new data centres a little time to learn the quickest route from a IP?

@Tim Lester - Depends on your network provider. Run a traceroute to your site and send it to us via help at cloudflare dot com and our network engineer can take a look.

A big congrats to people in Singapore and surrounding areas! :D

This is my traceroute to cloudflare powered website,
using Telkom Speedy, Indonesia's largest ISP ==>

Tracing route to xyz.com [199.27.135.87]
over a maximum of 30 hops:

1 <1><1><1>
2 * 42 ms 42 ms 125.166.160.1
3 41 ms 43 ms 42 ms 189.subnet125-160-14.speedy.telkom.net.id [125.160.14.189]
4 67 ms 69 ms 69 ms 62.subnet118-98-61.astinet.telkom.net.id [118.98.61.62]
5 115 ms 115 ms 115 ms 116.51.17.225
6 * 117 ms 119 ms ae-2.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.4.142]
7 * 140 ms 143 ms as-3.r20.osakjp01.jp.bb.gin.ntt.net [129.250.3.48]
8 * * 278 ms as-2.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.164]
9 263 ms 261 ms 255 ms ae-1.r07.snjsca04.us.bb.gin.ntt.net [129.250.5.53]
10 251 ms 248 ms 260 ms xe-7-0-2.ar2.sjc1.us.nlayer.net [69.22.153.176]
11 259 ms 255 ms 266 ms as13335.ge-0-0-37.ar2.sjc1.us.nlayer.net [69.22.153.74]
12 265 ms 254 ms 264 ms cf-199-27-135-87.cloudflare.com [199.27.135.87]

This is to a big hosting company in singapore ==>

Tracing route to somesingaporehostingcorp.com [120.50.40.40]
over a maximum of 30 hops:

1 <1><1><1>
2 41 ms 42 ms 42 ms 125.166.160.1
3 41 ms 42 ms 41 ms 189.subnet125-160-14.speedy.telkom.net.id [125.160.14.189]
4 * * 71 ms 62.subnet118-98-61.astinet.telkom.net.id [118.98.61.62]
5 70 ms 68 ms 69 ms p17547.sgw.equinix.com [202.79.197.16]
6 * * 69 ms 101.203-211-158.unknown.qala.com.sg [203.211.158.101]
7 186 ms 228 ms 220 ms gi-4-3.a020.m1net.com.sg [203.211.158.110]
8 70 ms 73 ms 73 ms r16-18-v23.sgsvr.com [111.235.136.78]
9 73 ms 72 ms 73 ms somesingaporehostingcorp.com [120.50.40.40]

Any idea? :)

That first tracert to a cloudflare website isn't an issue on CF end. From what appears, the problems are starting on hop #5 which could indicate routing issues with the way your data is being routed to said CF powered website.

odd, my requests from malaysia are hitting hongkong, when singapore is nearer.

i'm not even hitting the singapore datacenter from my server in singapore!

Tracing ........T
TTL LFT trace to cf-173-245-60-121.cloudflare.com (173.245.60.121):80/tcp
1 [AS?] [Net?] 180.92.186.41 0.3ms
2 [AS?] [Net?] 20.te1-1.tsr1.sin1.sg.voxel.net (72.26.220.9) 0.4ms
3 [AS?] [Net?] VDI-0001.asianetcom.net (203.192.169.233) 0.3ms
4 [AS?] [Net?] so-3-0-3-0.cr4.hkg3.asianetcom.net (202.147.16.101) 31.0ms
5 [AS?] [Net?] te3-2.gw1.hkg4.asianetcom.net (202.147.16.198) 31.3ms
6 [AS?] [Net?] CDF-0002.gw1.hkg4.asianetcom.net (202.147.17.182) 31.9ms
7 [AS?] [Net?] [target closed] cf-173-245-60-121.cloudflare.com (173.245.60.121):80 31.6ms

@paultantk: ya, same here. requests from Malaysia don't go thru Singapore datacenter.

liewcf: on Yes 4G, it's even stranger, the route goes through singapore, then off to japan, and finally lands at cloudflare's US datacenter!

macpro.local (0.0.0.0) Mon Sep 5 19:40:55 2011
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 4 0.4 0.3 0.2 0.4 0.1
2. 192.168.32.1 0.0% 4 0.8 0.8 0.7 0.9 0.1
3. ???
4. 172.20.196.1 0.0% 4 50.0 68.3 50.0 109.2 27.6
5. ???
6. 172.20.81.157 0.0% 4 55.7 61.2 47.0 78.5 13.4
7. 172.20.81.162 0.0% 4 46.5 56.9 35.9 88.6 22.8
8. 172.20.83.52 0.0% 3 70.1 76.0 70.1 80.9 5.5
9. 172.20.0.9 0.0% 3 90.0 64.6 34.6 90.0 28.0
10. 172.20.0.46 0.0% 3 41.4 59.8 41.4 80.7 19.8
11. ae-0.r02.kslrml01.my.bb.gin.ntt.net 0.0% 3 82.2 68.8 57.9 82.2 12.3
12. as-2.r02.sngpsi02.sg.bb.gin.ntt.net 0.0% 3 63.5 86.2 63.5 130.8 38.6
13. p64-2-1-0.r23.osakjp01.jp.bb.gin.ntt.net 0.0% 3 169.4 149.9 133.3 169.4 18.2
14. ae-7.r20.osakjp01.jp.bb.gin.ntt.net 0.0% 3 121.0 145.7 121.0 171.8 25.4
15. as-1.r21.snjsca04.us.bb.gin.ntt.net 0.0% 3 276.2 269.0 264.6 276.2 6.3
as-1.r20.lsanca03.us.bb.gin.ntt.net
16. ae-1.r04.lsanca03.us.bb.gin.ntt.net 0.0% 3 282.2 256.1 243.1 282.2 22.5
ae-1.r05.lsanca03.us.bb.gin.ntt.net
17. xe-2-0-2.ar1.lax2.us.nlayer.net 0.0% 3 258.0 275.1 235.8 331.4 50.0
xe-7-0-4.ar2.sjc1.us.nlayer.net
xe-7-0-5.ar2.sjc1.us.nlayer.net
18. 69.22.152.70 0.0% 3 238.7 239.1 230.5 248.2 8.8
ae1-50g.cr1.lax1.us.nlayer.net
19. ae1-50g.ar1.lax1.us.nlayer.net 0.0% 3 269.9 266.5 259.2 270.3 6.3
cf-173-245-60-121.cloudflare.com
20. as13335.ge-0-0-35.ar1.lax1.us.nlayer.net 0.0% 3 270.7 279.9 267.7 301.2 18.5
cf-173-245-60-121.cloudflare.com
21. cf-173-245-60-121.cloudflare.com 0.0%

And here it is from Time Broadband... also goes to the US datacenter

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.0.1 0.0% 10 1.3 21.2 1.3 110.8 37.8
2. 203.121.82.1 0.0% 10 19.5 36.1 16.8 140.9 40.3
3. 10.200.203.49 0.0% 10 17.7 28.2 16.8 84.4 23.4
4. ge-3-0-7.glsfb01.icr.time.net.my 0.0% 10 17.1 29.6 16.6 120.9 32.4
5. ae-2-0.er-01-glsfb.ni.time.net.my 0.0% 10 17.2 45.3 16.9 133.9 46.3
6. xe-0-1-0-0.cr-02-glsfb.ni.time.net.my 0.0% 10 20.7 32.4 20.5 84.4 21.7
7. xe-2-0-0-0.cr-01-astbb.ni.time.net.my 0.0% 10 20.0 42.2 18.9 137.3 44.6
8. xe-2-0-0-0.cr-01-csfcb.ni.time.net.my 0.0% 9 18.9 37.7 18.8 98.8 28.2
9. ae-2-0.br-01-csfcb.ni.time.net.my 0.0% 9 21.2 22.5 18.9 42.2 7.5
10. ae-1.edge-gw-2-cyberjaya-pip.my.globaltransit.net 0.0% 9 19.9 54.2 18.9 135.7 51.9
11. xe-0-0-0-0.edge-gw-1-cyberjaya-pip.my.globaltransit.net 0.0% 9 195.6 224.0 187.1 389.3 66.4
12. xe-0-0-2-0.cr-gw-1-kul-pip.my.globaltransit.net 0.0% 9 190.0 220.9 186.9 339.3 58.8
13. ae-1.cr-gw-1-sin-pip.sg.globaltransit.net 0.0% 9 187.1 219.0 186.5 290.5 47.9
14. ae-1.br-gw-1-lax-pip.us.globaltransit.net 0.0% 9 185.9 202.2 185.7 254.6 25.6
15. TenGigabitEthernet2-4.ar5.LAX1.gblx.net 0.0% 9 190.7 208.8 187.1 305.8 40.6
16. xe-3-0-3.ar1.lax1.us.nlayer.net 0.0% 9 194.4 215.9 191.6 314.0 44.6
17. as13335.ge-0-0-35.ar1.lax1.us.nlayer.net 0.0% 9 191.1 212.6 189.7 293.1 36.8
18. cf-173-245-60-121.cloudflare.com 0.0% 9 189.5 201.7 189.1 262.4 23.7

Thanks for letting us know. There was an issue with one of the routes to our Singapore Datacenter. We've corrected the problem and routing should be better again. If you see problems in the future, send the traceroutes to help (at) cloudflare (dot) com and it will get to our network engineering team quickly!

I am in Singapore Changi airport now, I am hitting a US datacenter it seems.

Tracing ........*..*.*..*T
TTL LFT trace to cf-173-245-60-15.cloudflare.com (173.245.60.15):80/tcp
1 [AS?] [NULL] 127.128.201.254 3.5ms
2 [4657] [Starhub-Ltd] 203.118.14.67 6.2ms
3 [4657] [StarHub] vlan911-an-cat6k-ts-2-rsm1.starhub.net.sg (203.118.5.4) 3.6ms
4 [4657] [StarHub] anutsi11.starhub.net.sg (203.118.3.227) 6.7ms
5 [2914] [NTTA-129-250] p16-7-1-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.12.69) 173.6ms
6 [2914] [NTTA-129-250] ae-3.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.155) 79.8ms
7 [2914] [NTTA-129-250] ae-3.r22.osakjp01.jp.bb.gin.ntt.net (129.250.3.220) 83.7ms
8 [2914] [NTTA-129-250] ae-2.r20.osakjp01.jp.bb.gin.ntt.net (129.250.2.2) 85.3ms
9 [2914] [NTTA-129-250] as-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.3.201) 188.4ms
10 [2914] [NTTA-129-250] ae-1.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.230) 184.7ms
** [neglected] no reply packets received from TTL 11
12 [4436] [NLYR-69-31-127-0-1] ae1-50g.cr1.lax1.us.nlayer.net (69.31.127.129) 277.4ms
** [neglected] no reply packets received from TTL 13
14 [4436] [NLYR-69-31-127-0-1] as13335.ge-0-0-34.ar1.lax1.us.nlayer.net (69.31.127.102) 237.5ms
15 [13335] [IANA-NETBLOCK-173] [target open] cf-173-245-60-15.cloudflare.com (173.245.60.15):80 244.3ms

great news, congratulations

In order to be routing efficiently in Singapore, you need to buy local transit from the telcos here. The major players guard their local consumer traffic closely.

Just look at the traceroute below, seems like they are accepting your prefixes via your upstream but chose to take another route when advertising their prefix.

On a side note, joining SGIX (http://www.sgix.sg) might have have some benefits, but irony is that it will benefit the Indonesians more because their upstream has an open peering policy ie the objective of SGIX.

traceroute to 199.27.135.80 (199.27.135.80), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.426 ms 2.159 ms 2.644 ms
2 * * *
3 246.246.65.202.unknown.m1.com.sg (202.65.246.246) 10.343 ms 7.393 ms 8.259 ms
4 245.246.65.202.unknown.m1.com.sg (202.65.246.245) 7.517 ms 7.144 ms 7.960 ms
5 38.246.65.202.unknown.m1.com.sg (202.65.246.38) 6.976 ms 5.848 ms 7.404 ms
6 54.246.65.202.unknown.m1.com.sg (202.65.246.54) 8.425 ms 7.577 ms 8.017 ms
7 if-0-1-9.core1.s9r-singapore.as6453.net (209.58.82.125) 8.234 ms
if-9-0-8.core1.s9r-singapore.as6453.net (209.58.82.105) 8.851 ms
if-0-1-9.core1.s9r-singapore.as6453.net (209.58.82.125) 8.654 ms
8 if-8-3-0-0.tcore1.svw-singapore.as6453.net (209.58.82.174) 181.284 ms 183.490 ms 182.947 ms
9 if-6-2.tcore2.tv2-tokyo.as6453.net (180.87.12.110) 188.393 ms 197.491 ms 185.111 ms
10 * if-2-2.tcore1.tv2-tokyo.as6453.net (180.87.180.1) 205.995 ms 186.251 ms
11 if-9-2.tcore2.pdi-paloalto.as6453.net (180.87.180.17) 207.865 ms 190.843 ms 224.793 ms
12 te1-4-10g.ar1.pao2.gblx.net (208.51.134.97) 185.820 ms 188.637 ms 188.793 ms
13 * * *
14 ae0-80g.cr1.pao1.us.nlayer.net (69.22.153.18) 187.551 ms 201.270 ms 199.067 ms
15 ae1-50g.cr1.sjc1.us.nlayer.net (69.22.143.165) 201.286 ms 187.995 ms 200.192 ms
16 ae1-40g.ar2.sjc1.us.nlayer.net (69.22.143.118) 204.005 ms 196.958 ms 212.164 ms
17 as13335.xe-8-0-5.ar2.sjc1.us.nlayer.net (69.22.130.146) 200.794 ms 209.461 ms 203.510 ms
18 cf-199-27-135-80.cloudflare.com (199.27.135.80) 207.126 ms 228.969 ms 209.928 ms

Hi,

Can you send us the IP address you did this trace from & the trace to our contact form? Our Network Engineer will see if we can fix this, but we need the source IP first.

http://support.cloudflare.com/cgi/discussion/new

Great! hopefully my site hosted in Singapore would see faster traffic now! Why wouldn't it?