These magical IPs are possible thanks to Google's edge network <https://peering.google.com/>. The edge network locations advertise themselves as a route to these IPs so a user's request will go straight into our network and reach the closest data center. This means the request will not need to traverse the internet to California and back to serve your users.
What results do you get when you try to ping or traceroute your application serving on the domain? On Monday, August 28, 2017 at 4:00:14 AM UTC-4, Dev Vercer wrote: > > > > On Saturday, August 26, 2017 at 2:01:38 AM UTC+10, Yannick (Cloud Platform > Support) wrote: >> >> >> There should be no need to use other IPs as your application will still >> serve traffic from the region it was created in. Was that your concern? >> > > I am worried that requests from users in the UK will be routed through the > US because the servers with these IP addresses are located there (according > to several location services). > > If this is not the case, how do these magical IP addresses work? ;) > > > >> >> I also believe this configuration allows for the use of subdomains for >> your App Engine services. >> > > Subdomains are configured with a CNAME ghs.googlehosted.com so I assume > this can return different IP addresses depending on where is is queried > from. i.e. from London the DNS could return IP addresses for local servers. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f0229b83-b69e-4f3a-9a88-ed0e1eadc210%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
