the forums at degreez.net

Just out of curiousity, are the 2 sites blocking certain ip ranges?

My home dsl can't reach the 2 sites anymore.

After hop #9...it goes...

7 ge-1-2-56.car1.Chicago1.Level3.net (4.68.101.162) 72.494 ms ge-1-1-51.car1.Chicago1.Level3.net (4.68.101.2) 71.685 ms ge-1-2-54.car1.Chicago1.Level3.net (4.68.101.98) 71.230 ms
8 4.79.72.42 (4.79.72.42) 118.852 ms 184.632 ms 122.475 ms
9 209.120.176.2 (209.120.176.2) 69.304 ms 71.366 ms 72.317 ms
10 * * *

I'm coming from the network below owned by covad...

67.100.*.*

I'm not blocking anything...

It's very Strange that I am not able to get to your site from my home dsl.

Below is what my ISP said...

Just FYI, I too can not access your site from my home Comcast Cable connection, something is blocking it, unless I use an anonymous surfing website. But on Qwest DSL at work I can get to it just fine.

You know, I forgot to mention that my bro is using Comcast and he is unable to get this site too.

Wonder what is going on?

I have the same problem with my cable ISP. I solved my problem by changing IE browser to a proxy server connection to this site. Read more from the following:

http://www.freeproxy.ru/en/free_proxy/howuse.htm

http://oink.me.uk:82/faq.php

Seems to work for me but don't ask me why. Hope it helps.

Would someone with this problem please run a couple of tests for me?

My service provider wants:

I take back what I posted earlier because I can't get to BitTornado site today thru cable connection. (I am on dialup at the moment)

THANKS SHADOW for looking into this probem.

I don't know much about computers. SO PLEASE somebody do these tests, PLEASE !!!

I did it.
I did a traceroute on bittornado site. Here it is:

Tracing route to www.bittornado.com [66.90.104.135]
over a maximum of 30 hops:

1 6 ms 5 ms 6 ms 10.*******
2 5 ms 5 ms 5 ms 24.28.97.165
3 7 ms 7 ms 5 ms 24.28.100.30
4 8 ms 7 ms 5 ms 24.93.33.148
5 22 ms 19 ms 18 ms 24.93.34.38
6 15 ms 15 ms 62 ms 67.72.0.57
7 16 ms 19 ms 112 ms 4.68.122.1
8 51 ms 51 ms 52 ms 64.159.4.225
9 62 ms 51 ms 51 ms 4.68.101.98
10 * 92 ms * 4.79.72.42
11 47 ms 47 ms 59 ms 209.120.176.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Looks like the problem lies in the FDC servers (line 11) located somewhere in Chicago. what next?

hesomagari: Can you traceroute to 66.90.64.1 as well, please?

Here is the trace for 66.90.64.1:

Tracing route to 66.90.64.1 over a maximum of 30 hops

1 5 ms 5 ms 5 ms 10.50.128.1
2 6 ms 5 ms 5 ms 24.28.97.165
3 7 ms 7 ms 5 ms 24.28.100.17
4 7 ms 9 ms 5 ms 24.93.33.147
5 7 ms 10 ms 7 ms 24.93.33.165
6 14 ms 23 ms 13 ms 24.93.34.25
7 12 ms 14 ms 13 ms 67.72.0.49
8 12 ms 11 ms 11 ms 4.68.122.1
9 49 ms 48 ms 49 ms 64.159.1.34
10 49 ms 49 ms 47 ms 4.68.101.98
11 * 85 ms * 4.79.72.42
12 44 ms 43 ms 45 ms 66.90.64.1

Trace complete.

This morning, I was able to contact by phone with Yipes Communication, Inc (209.120.176.2) at 1-877-788-4662. The nice person helped me forward my trace for bittornado to the FDC server people. I also called afterwards (312-913-9302) and the system manager (Rick) at FDC promised to get an engineer to check. There is a glimmer of hope in this mess.

Thanks SHADOW.

I am not sure 209.120.176.2 is Yipes or FDC. My cable ISP says if you type in the address in ARIN.Net(?) then you can find out the router's name. Something like that.

I think the problem's been resolved. Please try contacting bittornado.com again.