Really strange. For 3-4 weeks now I've not been able to connect to CURSE.COM ( site for gaming addons ).
So yesterday I called Rogers CS to ask about it. At first, the rep had no problems connecting from the T1 line at his terminal. To be safe though, he went and tried it from another terminal that used a different connection and he also timed out & could not connect ... so this helped to confirm that I wasn't going insane. He has escalated it to be looked at.
In the meanwhile, I thought I'd ask if anyone else has had this problem with CURSE in particular?
Yep, ran a tracert a couple of times and got through just fine. It's a really weird problem. Cannot connect directly to the url by name or IP from IE10. Tried running it in compatibility mode too and no effect.
Interestingly, I just thought of trying it via Chrome while answering you ... and it went through just fine. So maybe it's some kinda weird IE thing. Ah well. Guess this solves it lol.
FWIW, I just tried connecting to curse.com with IE 10 and Chrome. Neither one worked. I get the oops cannot connect message from both browsers.
Yea, it's a completely strange situation.
I still cannot connect from IE10 ... can connect from Chrome ... and my wife cannot connect from her Apple Safari. At the same time, I know that most people can connect and that it is just a few ISPs with the problem ( Rogers seeming to be one of them ).
No word back from Rogers yet on my escalation of this issue from a couple of days ago. If anyone figures this out in the meanwhile, please post it up!
Just tried it with Safari on my iPhone and no dice. The error message said "Safari could not open the page because the server stopped responding". Sounds like the issue is with the web site.
Just tested right now:
Loaded from work (bell, Bell DNS) works fine.
Loaded from home - remoted into home PC (rogers, GOOGLE DNS) works fine.
Makes me think DNS issue?
Try on Safari on iphone, on CELLULAR (rogers, rogers DNS) connets fine.
Sooooo.. really dont think its DNS per say.. unless speratic?
Otherwise... routing? where the routing goes down on it temporarily?
Or could just be the receiving end..
They are doing load balancing and have IPs in 2 different blocks - it's possible you're having issues with one of them which would explain why it's sporadic.
curse.com. 5M IN A 184.108.40.206
curse.com. 5M IN A 220.127.116.11
curse.com. 5M IN A 18.104.22.168
curse.com. 5M IN A 22.214.171.124
curse.com. 5M IN A 126.96.36.199
Try visting these by IP address. You should see a Cloiudflare custom error page if you are connecting OK.