This problem occurred a little over 24hours ago. Since there has been alot of little bits of downtime here and there I decided to wait it out and figured the site would come back up. However I went to check it again and I cannot access my website. I can access teh account itself, edit the pages but I cant view any of them when they are done. I keep getting the following message every time I try to access my pages

"Network Error (tcp_error)

 
A communication error occurred: "Operation timed out" 
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. 

For assistance, contact your network support team "

How long is this going to last?

Assuming your website name matches your posting ID here...

I accessed your website numerous times yesterday and today, from various routes in different countries, and your pages all loaded every time without any failure. (The only minor issue I noticed was yesterday lunch time GMT when your images were loading slowly, but I soon realised this was because you have hosted them on photobucket.com and not directly on T35 which is invariably always faster).

If you still cannot access your site, I would suggest you try other T35 member sites to see if they also fail. You can easily find other sites by doing a google search for site:t35.com

You might also consider posting the output of a traceroute here, and state where in the world you are based.

Does the main www.t35.com site work? It's hosted on a different IP.

Are you on a static IP? You may currently be using an IP that is banned by T35, although that seems very unlikely.

How far does a traceroute go?
(open a windows command prompt and type tracert yoursite.t35.com)

It should go all the way to the site. If it doesn't, post the output here (after optionally removing any personally identifying IP or domains used by you and your ISP).

It could also be a DNS issue. The IP in the first line of the tracert would reveal if this was the case.

Does the traceroute print this as it's first line of output?

Tracing route to yoursite.t35.com [IP-address]
over a maximum of X hops

If so, what's the IP it displays?

Hmm, that's the correct IP. Not a DNS issue.

If you don't want to post the traceroute here (in full, or edited for privacy) then I suggest you open a private support ticket and post the full traceroute there (this will only be seen by Alex). Also tell him what your IP is. You can see your own IP at http://whatsmyuseragent.com

Out of curiosity, what ISP are you using?

Perhaps.

But it could be your firewall. Your hosts file. Your other security software. Your ISP.

Without a traceroute, it would be hard for anyone to tell.

I assume you can browse your site through a proxy, such as http://www.anonymouse.org/ or http://www.unblockmyspace.com/

I have the same problem, ie, cannot loading any of the xxx.t35.com websites at all most of the time, or sometimes just loading very slowly.
I had a live chat with the T35 support team and they insist there are no problems at their end and said it was due to my own PC's admin or the ISP has blocked my IP address from the website. I gave the agent my IP address and he/she checked and confirmed to me that it was my Internet provider who blocked it. I told him/her that other viewers in different part of the UK report the same thing. He/she said they may all be blocked by their own ISP (how can it be). The agent  said it was the ISP I need to talk to, nothing to do with them and said bye, very rude.

I call my ISP support, they checked the web address and said it wasn't blocked, they have no policy to block such website in the UK.

I search and find that you guys are having the same problem, it is clear now where the problem is. It must be the T35 hosting are having some technical problems but do not want to admit as it may damage their business.

It looks like we have to move the site somewhere else.

hamsub: You haven't said who your ISP is. If like evolutionofwrestling it is also BT, then that would be a potential clue where the problem lies. If I were talking to someone at my ISPs support, I would ask them if they could browse the site in question from their machine rather than just asking them if they were blocking anything, and it it failed I'd want to know where in their traceroute it failed.

Also, it may not be that a particular ISP is actually blocking anything, but routeing tables do sometimes innocently get wrong entries in them (and often won't get fixed till someone reports it), and this would only affect those end-users whose ISPs were using those routes. I'm on Zen and currently see no such problems (any downtime I've seen at T35 has also been witnessed via multiple foreign proxies so was almost certainly genuine T35 downtime and generally doesn't last too long (probably a reboot or an attack)).

Without a traceroute, it's difficult for anyone to say how far the connection attempt gets before it dies. It may not even be getting as far as the border routers of your own ISP, which would place the fault definitely within the hands of your ISP (or at least, the resolution to the fault).

Sadly, even with a traceroute, it's not guaranteed that you'll pin-point where it goes wrong. My own traceroute has 10 hops. First is local, then 6 at my ISP, then 3 in the US including the destination IP, but only T35 support would be able to advise on whether the 8th and 9th are their responsibility or the responsibility of a service or backhaul provider.

I'd even suggest that your own ISP has a responsibility to investigate here. Given that the T35 sites clearly work (for other users, and for yourself via a proxy), your ISP (if they themselves cannot access the site directly) should pass a fault upstream to their transit provider, who can in turn pass it up to theirs till they find out where it's failing. Sadly getting support departments to help in this manner is a bit hit and miss.

As far as I know, 64.20.32.78 is the 2nd last step, and belongs to interserver.net who appear to be T35's connectivity/hosting/vps provider (I'm not sure exactly what configuration T35 run).

When you say "stopped", did it fail? or complete?

If it failed, I'd suggest that's a problem with interserver.net or T35

hamsub:

what ISP are you with?

I have seen some traceroutes stop at 64.20.32.78 just before the last hop, so there might not be a problem there (I did say earlier that traceroutes aren't always perfect for tracing problems).

You seem to suggest the problem is not permanent, in that sometimes it works, even if slowly. That would generally rule out an IP or domain block anywhere.