We’ve been using the San Jose test machine for months with relatively accurate results up until about 2 weeks ago. At that point we noticed high load times for certain images on the site and saw that these images were being pulled from our CDN’s (Akamai) server in Europe.
After going back and forth with Akamai we discovered that the San Jose machine you guys are using also uses Google name servers, which according to them are not accurately reporting the physical locations of these machines and thus pulling images from remote locations.
View Akamai’s response here:
Retrieved tier 1 diagnostics results from the customer Found the historical mapping information for the customer Found out that the Name Server of the Third Party tools that the customer is using is a GOOGLE INC. Name Server , and hence such requests are getting mapped not very optimally ( and out of the US at times).
Explained the talking points of the GOOGLE INC. Name Servers issue to the customer.
Customer confirmed that when they do a same test from another location on the test tool they get better performance,
had the customer submit the tier 1 diagnostics via the test tool from that location also - and confirmed that the Name Server was not a Google Inc. Name Server and hence the mapping was optimal. Explained to the customer to give this feed back to the Third Party Test Tool they are using.
One additional thing I should mention is that your newly added Los Angeles machine does not use Google name servers and is accurately pulling images from the correct locations and reporting the load times for the site that we’d expect to see.
Has anyone else using Akamai seen this issue?