DirecTV DSL → ATL down again....

May 02, 2001 09:15 - 09:55

Tracing route to dell.com [143.166.82.178]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms My SYS

2 16 ms 15 ms 16 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 16 ms 15 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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 79 ms 78 ms 78 ms rr-www.us.dell.com [143.166.82.178]
____________________________________________________________

2 16 ms 15 ms 16 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 16 ms 15 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 63 ms 62 ms 63 ms pos8-1-hfr2.dfw.tlct.net [216.227.126.22]
5 63 ms 62 ms 78 ms ge-v5-hfr1.dfw.tlct.net [216.227.126.53]
6 94 ms 109 ms 109 ms 216.227.126.161
7 93 ms 110 ms 109 ms ge-v5-hfr1.lax.tlct.net [216.227.126.49]
8 94 ms 109 ms 109 ms fe0-0-hfr0.lax.tlct.net [216.227.126.86]
9 109 ms 109 ms 110 ms pos4-0-pbnap.sjc.tlct.net [216.227.126.30]
10 109 ms 109 ms 125 ms fe5-1-hfr1.sjc.tlct.net [216.227.126.166]
11 109 ms 110 ms 109 ms pos2-1-paix.pao.tlct.net [216.227.126.210]
12 110 ms 109 ms 109 ms gblx-px.pao.tlct.net [64.192.16.14]
13 110 ms 109 ms 125 ms so1-0-0-622M.cr1.pao2.gblx.net [208.50.169.141]

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.
____________________________________________________________

Tracing route to My company website!
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms My SYS

2 16 ms 15 ms 16 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 15 ms 16 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 16 ms 16 ms 15 ms 63.211.121.5
5 47 ms 47 ms 63 ms so-0-0-0.mp1.Dallas1.level3.net [209.247.8.29]
6 47 ms 46 ms 63 ms so-0-0-0.mp1.Dallas1.level3.net [209.247.8.29]
7 47 ms 47 ms 62 ms pos8-0.core1.Dallas1.level3.net [209.247.10.98]

8 47 ms 47 ms 62 ms acr1-serial6-0-0-0.Dallasdan.cw.net [208.172.131
.225]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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.
____________________________________________________________

Tracing route to telocity.com [216.227.62.81]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms My SYS

2 15 ms 16 ms 16 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 15 ms 16 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 62 ms 63 ms 78 ms pos8-1-hfr2.dfw.tlct.net [216.227.126.22]
5 62 ms 63 ms 78 ms ge-v5-hfr1.dfw.tlct.net [216.227.126.53]
6 94 ms 109 ms 110 ms 216.227.126.161
7 94 ms 109 ms 109 ms ge-v5-hfr1.lax.tlct.net [216.227.126.49]
8 93 ms 157 ms 93 ms fe0-0-hfr0.lax.tlct.net [216.227.126.86]
9 109 ms 110 ms 125 ms pos4-0-pbnap.sjc.tlct.net [216.227.126.30]
10 109 ms 109 ms 110 ms fe5-1-hfr1.sjc.tlct.net [216.227.126.166]
11 109 ms 110 ms 109 ms 216.227.63.17
12 110 ms 109 ms 110 ms 216.227.62.81

Trace complete.
____________________________________________________________

Tracing route to msn.com [207.46.185.39]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms My SYS

2 16 ms 15 ms 16 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 15 ms 16 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 110 ms 125 ms 109 ms 4.24.9.157
15 125 ms 141 ms 140 ms p5-0.evrtwa1-ba1.bbnplanet.net [4.24.9.174]
16 125 ms 172 ms 140 ms p1-0.evrtwa1-cr1.bbnplanet.net [4.24.5.102]
17 125 ms 140 ms 141 ms p2-0.mscanyonpark.bbnplanet.net [4.24.125.66]
18 125 ms 141 ms 140 ms 207.46.129.177
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.
____________________________________________________________

We don't like the messages so let kill the messenger. Yes, it an overused cliche.

Okay, boys and girls, we see all these times outs in the trace routes, except they happen after telocity is no longer handling the hops.

Hey, I have done trace routes to a few of these sites and other very popular web site and got the same results. What surprise me is that even with s***ty hops, the pages open without problems.

Unfortunately, this happens several times a day for 5 minutes to 8 hours or more. I can't open sites and can't reach s&*t. My DSL connection will drop or might as well have when this happens.

I am looking to go to BS and drop telocity after only 6 weeks of service.

Winfire was more stable than this... well until March 8th at least.

When I'm up I'm happy... and the speeds are ok to great..

Hello My Fellow Georgian,

Just to add input. I too, had the same symptoms you are
experiencing. I contacted Telocity, and they could find no problems. The situation began last Wed. and continued until yesterday.

I finally convinced Bellsouth to do some checking and they found a "bad" connection on their "drop" to my house. They replaced the drop with new wire and all problems disappeared.

Many are the times that Telocity is blamed, when the real culprit is the telco.

Yes, I am routed thru the same Atlanta routers as you, only further away.

Just a little "food" for thought! I hope your problem is corrected soon.

jnich1042
Thomson, Ga.

And AGAIN... This is not pointing to my line or systems...

It is flat out f***ed routing..

When I hit the preview button to submit this... 4 minutes later I was able to post!

2 16 ms 16 ms 15 ms route-64-129-143-1.telocity.com [64.129.143.1]
3 16 ms 15 ms 16 ms fe1-2-core1.atl.tlct.net [216.227.49.65]
4 15 ms 16 ms 16 ms 63.211.121.5
5 46 ms 47 ms 63 ms so-0-0-0.mp1.Dallas1.level3.net [209.247.8.29]
6 47 ms 47 ms 62 ms 209.247.8.29
7 47 ms 47 ms 63 ms pos8-0.core1.Dallas1.level3.net [209.247.10.98]

8 47 ms 46 ms 63 ms acr1-serial6-0-0-0.Dallasdan.cw.net [208.172.131
.225]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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.

I called T and there was a message that BellSouth users were experiencing an outage tonight...

What about the last few weeks of up and down..

The funny part is during the outage tonight I was able to hit ebay and a few other sites without a problem. I would try a tracert to different servers and I would have about 10-15 non replies and then it would continue!

I am thinking bellsouth is where I should have gone!

I'm having very similar symptoms to what you are describing. I, too, get routed through Atlanta for most stuff (sometimes, but rarely, Dallas). Anyway, my last few days have been really bad, worse then any time since I started with T (mid Feb, 2001). Look at this crap over the last day and a half:

Look's like your actually doing a little better than I am. I've been with Telocity since August and this is the worst it's ever been.

You may want to rethink going to Bell South.
I am a BS user and am thinking of going to Telocity. Not much improvement on this side. I got fast access in March of 2000. I sold and move in November of 2000. It took me until April of 2001 to get my service back. I was using my BS account on a 56k modem. Last week they sent us a message to tell us that if we use our dial-up connection in place of fast access, we will be billed extra. They also increased the cost of our fast access service at the same time. You should go to the newsgroup for BS.
news1.lig.bellsouth.net

Just a little information to let you know. I am thinking that maybe most providers are having problems with providing good service. I am looking around here to decide whether or not to stay with BS. Now I don't know what I will do.
Jaci

The routing seems to be fixed... I don't go to DFW to get to my server in Atlanta anymore. I am routed thru Washington on Level3 and then to CW to get to my server. My hops dropped 3 but I still get 47ms to my web server. (it is hosted at a friends ISP in Atlanta)

Since getting telocity, I tolerate the weirdness of ADSL service. To a certain extend, I share others beliefs that telocity is a p*** poor ran company. But, I can't get cable and I'm only paying $39.99 for service right now.

While it nice to get great speeds, especially for downloading, I hope everyone realize these DSL companies set themselves up on a Internet, IMHO that can't handle the traffic. I would compare it to how traffic jams are created when new houses go up in corn fields and people still work near a major city.

Hey, I wish telocity could doing better routing. Except, I figure premium low traffic networking cost big bucks.
[text was edited by author 2001-05-04 21:05:18]