View Full Version : tvrage.com blocked again
the number of sites iv had to use a proxy to access is getting a bit annoying
iv tried third party dns servers but theyve been a bit slower than the service im paying for
tvrage is working fine on VM in Leeds.
It's working fine in Middlesbrough, too.
Its failing here in Warrington.
Not working in Cambridge.
Working here, I've lost another site unless I proxy though, and DNS is correct on it, traceroute works, just won't go through without proxy.
giveawayoftheday.com
These routing foulups, or maybe censorproxy foulups, are becoming rather tiresome, thought we'd seen the end of fiddling with proxies when they got rid of the forced transparent proxying.
I have lost loads of sites tonight unless i use the proxy. Come on VM buck your ideas up and fix your routing out of Baguley
grubbymitts
09-09-2010, 20:47
Yeah, had to use webcache.virginmedia.com port 8080 to surf some sites today. Grrr
Working in Harlow, and our feed comes via Cambridge
Same problem in Sheffield the page just won't load
Working in Harlow, and our feed comes via Cambridge
Strange it's not working for me then.
TV Rage is not Blocked :rolleyes: please do not be so dramatic when problems occur.
JFYI, I could not access the site yesterday, but its fine today. Do I think VM deliberately blocked it ? of course not.
Not deliberately, but you wonder if the transparent proxies have been quietly returned, as it's the same kind of foulups - works from there, not from here, works if you switch proxies.
TV Rage is not Blocked :rolleyes: please do not be so dramatic when problems occur.
JFYI, I could not access the site yesterday, but its fine today. Do I think VM deliberately blocked it ? of course not.
:clap:
Chrysalis
10-09-2010, 15:49
indeed like the other nforce thread the term blocked is wrong.
TV Rage is not Blocked :rolleyes: please do not be so dramatic when problems occur.
JFYI, I could not access the site yesterday, but its fine today. Do I think VM deliberately blocked it ? of course not.
i agree blocked is the wrong term but its simple and straightforward and gets the message across that its a VM problem
"inaccessible on certain VM connections" is a bit long winded for a topic title
anyway seems to be working now
i agree blocked is the wrong term but its simple and straightforward and gets the message across that its a VM problem
"inaccessible on certain VM connections" is a bit long winded for a topic title
anyway seems to be working now
But more accurate....;)
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.