Can't access site sometimes.

For a few days now, I've been unable to load the beeradvocate site from any device behind my home router. I can assure you that I have verified this - so my question is whether my router's IP address has been banned for some reason?

Thanks,
Brady

 

I too am just wondering if something has changed on the server side.

 

No, I get the following, as of this morning:

1. Main Beeradvocate page: Cloudfare archive copy
2. Review listings: 'Error - BeerAdvocate has experienced an error. Doh!'
3. Forum: Top banner loads, maybe, and then stops.

 

So you're saying that something like #2 above is not a BA server error message?

 

It says it right there - upon trying to load my beer review listing page, I get that rather specific error (mostly due to the appending of the 'Doh'). Is that a BA error?

 

Here is the remainder of the error page:

-----------------------------------------------------------------------------------------
This website is offline
No cached version is available.

The most likely causes:

• The server is down for maintenance
• There may be a network problem
• The site may be experiencing excessive load

Retry for a live version of the site
We apologize for the inconvenience. Please try again in a few minutes.
------------------------------------------------------------------------------------------

You can see why I didn't take it seriously after 5 days of this now.

 

By which I mean, none of the likely causes, are in fact, the cause, save the second one, which is too general to be helpful.

 

Doing a trace route for both router-enabled and direct modem connections, I get the following CloudFlare servers at the last hop before beeradvocate.com:

Router: 7 111 ms 201 ms 206 ms six.as13335.com [206.81.81.10]

Modem: 7 57 ms 46 ms 45 ms cloudflare.torontointernetxchange.net [206.108.34.208]

The direct modem connection works, and the router doesn't - does this help?

 

I've contacted my ISP, but they weren't inclined to offer help, given that the direct modem connection worked.

Anyways, now suddenly everything works behind my router, even though the trace routes are the same, my IP and MAC address haven't changed, etc. I guess somewhere on the internet, a snag was cleared up. Thanks for your attention on the matter!