Request Timeout

I can't even ping the server however your DNS records point to 199.27.134.73 which is a cloud flare IP so I suggest contacting them.

Thanks for the reply. I took the website off Cloudflare and changed the nameservers, and rebooted the Linode, but I still cannot connect. I am able to ping the website successfully, if that helps.

Still shows as cloudflare for me so DNS hasn't updated on my end, I checked the new DNS records which point to 173.230.152.150 putting that IP in works fine so I'd assume you have some sort of page/DNS cache thats causing it to fail on your end, I imagine it will start working soon. You should still contact cloudflare and ask them what happened.

@obs:

Still shows as cloudflare for me so DNS hasn't updated on my end, I checked the new DNS records which point to 173.230.152.150 putting that IP in works fine so I'd assume you have some sort of page/DNS cache thats causing it to fail on your end, I imagine it will start working soon. You should still contact cloudflare and ask them what happened.

Alright thanks. Do you know approximately how long it will take for the DNS to fix itself?

Anything from 5 minutes to a day normally, depending on each connecting user's ISP.

Your site is coming up quickly for me and hosted on Linode.

@noodleboy347:

I have a website that has been working fine for a long time, but since last night many people have started having issues connecting to it. The strange part was that I was able to connect fine and some other people were too, but many people complained that the website wasn't working at all.

Since today I haven't been able to connect to the website either, but when I rebooted my Linode I was able to connect for about 5 minutes until it went down again.

The website in question is here:

http://goldenmachinegun.com

Thought I would jump in to address some concerns about testing to see if it is CloudFlare or not.

Things to check:

1. Try going direct.yourdomain.com. If the site doesn't load going direct, then the problem is with your server or hosting provider.

2. See what kind of message you get using this curl command in terminal:

curl -v -A firefox/4.0 -H 'Host: yourdomain.com' yourIP address

A can't connect to host message would mean the issue is with your hosting provider or server.

3. If you can go direct to your server and get an HTML response back in your curl, then the problem is likely that you have something blocking CloudFlare requests on your server and/or with your host (htacess, firewall, iptables, etc.). Some things to check can be found here: http://www.cloudflare.com/wiki/I_keep_s … Offline%22">http://www.cloudflare.com/wiki/Ikeepseeing%22MySiteisOffline%22

Another way to quickly test things is to login to your CloudFlare account & temporarily deactivate so we also go direct (settings->deactivate). If problem persists, then it is most certainly a host or server issue as well.

Direct works fine. People are able to get onto the site now but sometimes it's going down. I'm pretty sure it will resolve itself soonish.

@noodleboy347:

Direct works fine. People are able to get onto the site now but sometimes it's going down. I'm pretty sure it will resolve itself soonish.

Try curling your server when a blip is happening. Might give some additional insight.