Comic Discussion > QUESTIONABLE CONTENT
WCDT: 2480-2484 (1-5 July, 2013) Weekly Comic Discussion Thread
pwhodges:
--- Quote from: ankhtahr on 03 Jul 2013, 09:09 ---Damn, something's definitely wrong with the hosting of this comic. It took me now ten hours to read today's comic and enter the forum.
--- End quote ---
The CloudFlare caching service that the comic (and forum, as it's on the same server) uses has had problems at multiple nodes of its infrastructure today. There were two hours when I couldn't connect at all. Their status page still shows service degradation at a number of their nodes, including Frankfurt.
bhtooefr:
And I had problems earlier, as well.
And I also pointed out panel 3 earlier. :P
Masterpiece:
--- Quote from: ankhtahr on 03 Jul 2013, 09:09 ---Damn, something's definitely wrong with the hosting of this comic. It took me now ten hours to read today's comic and enter the forum. I was able to open the forum for a short time in between, but only the main page, I couldn't load any of the subforums. I sincerely hope that this post will come through…
Pings and TCP connections time out all the time, on both domains, questionablecontent.net and forums.questionablecontent.net. I'm surprised nobody seems to have these problems, as the problem occured device and ISP independent here. Not even webproxies or VPN helped…
--- End quote ---
I've had the exact same problems...
--- Quote from: pwhodges on 03 Jul 2013, 09:15 ---The CloudFlare caching service that the comic (and forum, as it's on the same server) uses has had problems at multiple nodes of its infrastructure today. There were two hours when I couldn't connect at all. Their status page still shows service degradation at a number of their nodes, including Frankfurt.
--- End quote ---
...but suspected correctly that it was just CloudFlare acting up. Was kinda annoying though! I was occasionally able to read your comments here and was aching to find more (confessed shipper here. Hi, GM!)
ankhtahr:
I totally oversaw that… Sorry.
So I wasn't the only one who had trouble with accessing from Germany today. When they know that this problem exists, why don't they resolve the domain to one of their working servers? The first ping I sent today was fine, but the following ones (which were sent to a different IP) all timed out. Entering the first IP in a browser resulted in a Cloudflare message that told me that direct IP connections are forbidden. This just confirms my opinion about services like this. I do not have much experience with this, but I think a well configured iptables should work against small DDoS attacks just as well as a caching service. Big DDoS attacks, well, they could just as well crash the caching service.
bhtooefr:
CloudFlare is also a hedge against IPv4 exhaustion - they actually care what hostname you access the site under, to determine how to route the traffic, using fewer IPs. In other words, with CloudFlare, the hostname is actually critical.
(And, FWIW, my problems were from Newark, OH, USA.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version