facebook apps that using linode ?

I'm not developing any FB apps, but here's a traceroute to api.facebook.com from fremont:

traceroute to api.facebook.com (69.63.180.23), 30 hops max, 40 byte packets
 1  gateway-he-li3.linode.com (64.62.190.1)  0.646 ms  0.814 ms  1.077 ms
 2  10gigabitethernet1-2.core1.sjc2.he.net (72.52.92.110)  0.723 ms  0.802 ms  0.876 ms
 3  sv1.br01.sjc1.tfbnw.net (206.223.116.166)  0.910 ms  0.898 ms  0.918 ms
 4  xe-0-3-0.br02.sjeq.tfbnw.net (204.15.20.7)  1.092 ms xe-1-0-0.br01.snc1.tfbnw.net (204.15.23.244)  1.393 ms  1.384 ms
 5  te-13-0.csw07b.snc1.tfbnw.net (204.15.22.14)  11.495 ms xe-10-3-0.br02.snc1.tfbnw.net (204.15.21.92)  1.610 ms  1.602 ms
 6  te-11-15.csw07a.snc1.sf2p.tfbnw.net (204.15.20.83)  1.685 ms api.11.07.snc1.facebook.com (69.63.180.23)  2.306 ms  3.548 ms

looks like the FB servers are in the bay area somewhere. relatively close to the fremont DC.

They're in San Jose, and Hurricane has a peering with Facebook (directly) right in San Jose. Fremont will be the fastest DC for Facebook hands down. Packets get there in ~1ms, the rest is latency inside Facebook's internal network.

thanks guy , this piece of info is helpful.

@jed:

They're in San Jose, and Hurricane has a peering with Facebook (directly) right in San Jose. Fremont will be the fastest DC for Facebook hands down. Packets get there in ~1ms, the rest is latency inside Facebook's internal network.

The API servers, sure. When I traceroute Facebook, it ends in Nashua, New Hampshire. Although when I traceroute the API servers, it still ends in the same place as you.