I'm trying to open my website, say example.com, and the request is timing out. However, www.example.com is opening fine. Also, both domains are working fine when using through a proxy (also working on isitdownrightnow.com)

I tried a traceroute on the two domains, and here is the output:

traceroute example.com
traceroute: Warning: example.com has multiple addresses; using
traceroute to example.com (, 64 hops max, 52 byte packets
 1 (  3.860 ms  3.179 ms  3.562 ms
 2 (  1.675 ms  1.707 ms  1.821 ms
 3  * * *
 4  * * *
 5  * * *

traceroute www.example.com
traceroute to ghs.googlehosted.com (, 64 hops max, 52 byte packets
 1 (  7.309 ms  8.445 ms  5.587 ms
 2 (  28.769 ms  14.107 ms  14.272 ms
 3 (  5.527 ms  9.530 ms  3.802 ms
 4 (  3.944 ms  3.702 ms (  8.681 ms
 5 (  7.606 ms (  4.416 ms  2.825 ms
 6 (  2.962 ms  2.700 ms
    w118012013.w118012.starhub.net.sg (  3.219 ms
 7 (  11.270 ms  3.088 ms (  6.476 ms
 8 (  18.269 ms
    anutli12.starhub.net.sg (  83.018 ms (  6.780 ms
 9 (  5.736 ms (  34.457 ms (  3.734 ms
10 (  11.556 ms  31.664 ms  28.546 ms
11  sin11s04-in-f115.1e100.net (  9.310 ms  40.297 ms (  9.148 ms

FYI, the site is hosted on Google Cloud. The DNS records consist of an A record for example.com pointing to 4 Google IPs, and a CNAME record for www.example.com that points to ghs.googlehosted.com.

I was wondering what could be the problem here, why is the request failing for example.com?

Any tips in the right direction would be helpful.


I'm trying to open my website, say example.com, and the request is timing out. However, www.example.com is opening fine.

You do appear to have four A records for example.com (quizziz) and one CNAME for www.example.com, so this makes sense.

The most likely explanation for your general problem is that one or more of the four addresses for example.com isn't working properly (it is not correctly handling the request for some reason or connections to that address are failing or timing out).

Unfortunately, multiple A records are handed out randomly and do not necessarily mean your requests get routed to a "good" address automatically.

Also, both domains are working fine when using through a proxy (also working on https://www.isitdownrightnow.com)

Without knowing which address is actually being contacted, this may not mean anything reliable for example.com. And in this case, it seems we have established the www version with the CNAME works.


  • Requests seemed to take a long time to work their way through Google's system. This could be causing time outs. I definitely experienced two connection timeouts in the browser (visiting the both the www and non-www versions of site) and was forced to reload the page to finish loading content.

  • seemed to work fine in-browser for me, in addition to the CNAME. I was not able to force the browser into testing the other IPs unfortunately.

  • Even though I checked your DNS records, and all apparently had the correct gateway Google IPs (32, 34, 36, 38), I did get routed one time to (Liquid Web Dedicated Hosting). Just a guess but this might be an older record cached somewhere else that hasn't expired yet.


My normal suggestion would be to test each address individually and try to find any culprit(s) that may not be working correctly.

However, these are generic Google gateway addresses for its services. Unfortunately, you may need to work with Google to resolve this.

Also, I would make sure your own network was handling the requests properly.

  • Thanks for the detailed reply. I edited my hosts file to try each IP individually, and all were working. I'm not sure how you got routed to the other IP (, but as you suggested, perhaps it is some old cached record. But seeing the logs of my failed requests, they were resolving to So I'm still stumped. Any other ideas? Jul 31 '17 at 14:55
  • Unfortunately, not at the moment, other than maybe contacting Google if you can. If their gateway is failing to route things to your site, they may have fix it. Since you said you altered the hosts file and got things working, the other possibility is some local network issue with resolution, though I don't know what that would be. Jul 31 '17 at 22:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.