For about two weeks now I have been trying to access the new igokisen web site to no avail,

I ran a traceroute with the following results:
------------------------------------------------------------------------------------------------------
traceroute to igokisen.web.fc2.com (208.71.106.61), 30 hops max, 60 byte packets
1 192.168.145.1 (192.168.145.1) 0.149 ms 0.119 ms 0.117 ms
2 192.168.0.1 (192.168.0.1) 1.307 ms 1.308 ms 1.311 ms
3 adsl-76-193-167-254.dsl.chcgil.sbcglobal.net (76.193.167.254) 45.894 ms 49.726 ms 52.598 ms
4 99.164.168.1 (99.164.168.1) 56.730 ms 59.662 ms 62.543 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
...
-------------------------------------------------------------------------------------------------------

so it appears to terminate at 99.164.168.1 where a whois search indicates is a Joliet AT&T substation.

Of course the traceroute indicates that I am also an AT&T ( from SBC ) subscriber.

Yesterday I tried to contact technical support ( turns out they have a sort of chat thingy on their support website ). There I was repeatedly told that AT&T does not block web sites, ( I never said they did it deliberately, or even that they were blocking web sites. Just that I couldn't access the web site. ) and to contact the domain provider, which I guess is the igokisen administrator. I have no idea how to contact him, and I don't think he can fix it even if I do given, given it is dieing at a AT&T station.

So I have two questions, the first being the obvious, how do I get this fixed? The second being my own curiousity. I know others in Chicago cannot access it, and I am curious how far this problem goes. Can you access the igokisen website? Where are you and what ISP are you using?

Thanks.

Rocky Mount NC, can connect, service provider is Century Link.

Edit: and traceroute works with igokisen.web.fc2.com to be perfectly clear.

_________________
Occupy Babel!

To make sure: http://igokisen.web.fc2.com/news.html

Is this the link you have been using? It might be possible you're off by something.

http://downforeveryoneorjustme.com/igokisen.web.fc2.com

--- (edit 1) ---

You can read up on browsing through a proxy.

I don't regularly use proxies. So I am not really the person you want to be learning from. But some minimal effort searching got me this site, which is working for me.
http://www.proxybrowsing.com/

--- (edit 2) ---

Now, the interesting thing is, even though I can fetch the webpage at home, I can not traceroute from my home! I don't understand that at all.

$ traceroute igokisen.web.fc2.com
traceroute to igokisen.web.fc2.com (208.71.106.61), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2.661 ms 0.700 ms 0.549 ms
2 (rubin427's IP address, which you don't need to know) 9.422 ms 13.510 ms 12.178 ms
3 24-234-8-9.ptp.lvcm.net (24.234.8.9) 9.832 ms 10.776 ms 10.677 ms
4 24-234-6-173.ptp.lvcm.net (24.234.6.173) 10.453 ms
24-234-6-169.ptp.lvcm.net (24.234.6.169) 10.513 ms 9.871 ms
5 langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) 16.533 ms 14.942 ms 16.180 ms
6 209.197.4.106 (209.197.4.106) 16.127 ms 14.798 ms
209.197.4.110 (209.197.4.110) 16.687 ms
7 208.71.106.17 (208.71.106.17) 16.635 ms 18.289 ms 15.310 ms
8 * * *
remaining hops timeout.

I read the man page for traceroute to see if I could specify port 80 (for typical web traffic). I did that and got one hop further, but I still mostly timeout.