It's hard to know for sure, but it looks to me like GAE apps are served at least somewhat locally.
Trace to one of my apps from a server in AZ, US: 1 64.34.162.131 (64.34.162.131) 0.718 ms 0.555 ms 0.527 ms 2 1ge-gi2-22.wdc-sp2-cor-2.peer1.net (216.187.120.249) 0.779 ms 0.612 ms * 3 10ge.xe-2-0-0.nyc-telx-dis-1.peer1.net (216.187.115.221) 5.898 ms 5.964 ms 5.845 ms 4 64.34.44.126 (64.34.44.126) 197.317 ms 105.316 ms 5.974 ms 5 72.14.239.46 (72.14.239.46) 6.514 ms 6.118 ms 6.157 ms 6 *Icmp checksum is wrong 209.85.249.11 (209.85.249.11) 8.402 msIcmp checksum is wrong 8.161 ms 7 209.85.248.75 (209.85.248.75) 19.720 ms 209.85.248.73 (209.85.248.73) 19.908 ms 19.617 ms 8 * 209.85.254.233 (209.85.254.233) 19.654 ms 209.85.254.239 (209.85.254.239) 19.587 ms 9 216.239.46.78 (216.239.46.78) 21.203 ms 28.852 ms 19.693 ms 10 * qw-in-f141.google.com (74.125.93.141) 19.799 ms 19.769 ms >From a site in Austria: 1 hq (213.235.199.19) 0.059 ms 0.028 ms 0.020 ms 2 Ge2-1-c2.oe3.sil.at (86.59.127.153) 0.361 ms 0.398 ms 0.547 ms 3 de-cix10.net.google.com (80.81.192.108) 23.925 ms 15.261 ms 15.568 ms 4 209.85.255.172 (209.85.255.172) 15.713 ms 209.85.255.170 (209.85.255.170) 16.127 ms 16.015 ms 5 72.14.232.201 (72.14.232.201) 15.810 ms 15.782 ms 72.14.232.165 (72.14.232.165) 16.033 ms 6 209.85.250.46 (209.85.250.46) 21.511 ms 27.661 ms 72.14.232.194 (72.14.232.194) 27.695 ms 7 fg-in-f141.google.com (72.14.221.141) 16.406 ms 15.992 ms 15.805 ms And to the OP's question, one from South Africa: 1 cisrb1-net109-64.posix.co.za (160.124.109.126) 0.185 ms 0.241 ms 0.224 ms 2 cisldn1-cisrbc1.posix.co.za (160.124.1.2) 167.005 ms 166.704 ms 167.003 ms 3 de-cix10.net.google.com (80.81.192.108) 178.228 ms 178.028 ms 178.479 ms 4 209.85.255.172 (209.85.255.172) 178.583 ms 209.85.255.170 (209.85.255.170) 178.672 ms 178.861 ms 5 72.14.232.208 (72.14.232.208) 192.585 ms 209.85.248.182 (209.85.248.182) 185.017 ms 185.251 ms 6 72.14.232.130 (72.14.232.130) 189.842 ms 189.803 ms 191.241 ms 7 209.85.251.231 (209.85.251.231) 189.712 ms 72.14.236.191 (72.14.236.191) 191.885 ms * 8 * 209.85.243.81 (209.85.243.81) 199.829 ms 209.85.243.73 (209.85.243.73) 200.722 ms 9 ww-in-f141.google.com (209.85.229.141) 190.988 ms 190.207 ms 190.185 ms Note that, on this last one, the latency doesn't increase all that significantly from the second hop all the way to the destination hop, and the third hop is "de-cix10", which *might* mean that it's a peering point in Germany. The end-point is only 34ms further than that, which implies to me that it's somewhere in Europe, though interestingly enough, it's not the same one that's at the end of the Austria trace. For more detective work, check out the int'l traceroute sites at http://www.traceroute.org. -Bne On Apr 30, 12:35 pm, Wooble <geoffsp...@gmail.com> wrote: > On Apr 30, 8:08 am, Martin <martin.konz...@gmail.com> wrote: > > > 1. How stable is the availability of apps down in Sub Saharan Africa; > > does Google have server-farms there, or is the traffic just routed to > > data-center somewhere in the Middle East? > > I don't believe Google's going to reveal any information on server > location, but my impression is that most of not all of the servers > doing app engine serving now are in the US. I could be completely > wrong. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
