EndLoser
join:2001-12-29
Richardson, TX
|  reply to yellow_cloud
Re: Garland Problems?
I posted this on another thread, but all of you having these problems definitely need to call ATT or Comcast or whoever they are now and complain loudly. I've tried to get ATT to fix this since January 23rd and they've sent a truck out twice and opened a network level trouble ticket once - still sucks. It'll be great for a day, maybe two and then crap for two or three days. This morning my speeds were 1700up and 220down - now they look like this:
2003-02-26 12:41:36 EST: 277 / 170
Your download speed : 277318 bps, or 277 kbps.
A 34.4 KB/sec transfer rate.
Your upload speed : 170226 bps, or 170 kbps.
or this:
2003-02-26 12:45:19 EST: 465 / 171
Your download speed : 465143 bps, or 465 kbps.
A 56.7 KB/sec transfer rate.
Your upload speed : 171718 bps, or 171 kbps.
From earlier post:
_______________________________________________
Perhaps it's just me, but I haven't seen anything happen to my connection (far east Richardson) that makes me believe any of my problems have been fixed. Here are my last three speed tests using DSLR (pretty typical):
2003-02-25 11:35:51 EST: 300 / 235
2003-02-25 11:37:18 EST: 404 / 175
2003-02-25 15:11:27 EST: 594 / 149
I've been after AT&T since January 23rd to find and fix this sh!t but get nowhere with them. Every time I call the problem in they want to roll a truck - every time the truck shows up the problem automagically disappears (until the technician leaves). My uploads haven't been the problem - it's always been the downloads. Sometimes I have speeds of 1800+ kbps while most times I get the crap above. I almost always have packet loss of between 2%-6% to every hop I try on AT&T's network.
Here are some tracert's from just last evening and this morning:
Tracing route to www.nasa.gov.att-idns.net [12.120.101.15]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms xxx.xxx.xxx.xxx
2 30 ms 30 ms 61 ms 10.180.192.1
3 30 ms 40 ms 40 ms 12.244.113.33
4 50 ms 40 ms 70 ms 12.244.73.13
5 60 ms * 51 ms gbr5-p30.dlstx.ip.att.net [12.123.17.50]
6 * * * Request timed out.
7 * * * Request timed out.
8 1672 ms 2934 ms 2925 ms tbr2.p013801.cgcil.ip.att.net [12.122.10.45]
9 260 ms 1022 ms 1943 ms tbr2.p013701.cb1ma.ip.att.net [12.122.10.105]
10 * * * Request timed out.
11 * * * Request timed out.
etc, or how about this crap...
Tracing route to pages.ebay.com [66.135.192.83]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms xxx.xxx.xxx.xxx
2 50 ms 30 ms 61 ms 10.180.192.1
3 30 ms 40 ms 40 ms 12.244.113.33
4 50 ms 40 ms 70 ms 12.244.73.13
5 2674 ms 2494 ms 441 ms tbr1.p012701.dlstx.ip.att.net [12.122.12.69]
6 * * * Request timed out.
7 30 ms 50 ms 20 ms ggr1-p340.dlstx.ip.att.net [12.122.12.74]
8 90 ms 70 ms 60 ms pos1-3.core1.Dallas1.Level3.net [209.245.240.173]
9 60 ms 51 ms 50 ms so-4-0-0.mp2.Dallas1.Level3.net [209.247.10.105]
10 * * * Request timed out.
11 * * * Request timed out.
I've never had such a bad problem with AT&T's service - guess I was due. I don't know about anyone else, but if I had a network that looked this bad I think I'd be embarrassed. I guess Comcast's web site was right - they said you could expect no changes in service after the merger and that's what I've seen in the past month - no changes.
Meanwhile a technician will once again be visiting in two days (Thursday 2/27/03) - most likely the problem will once be magically fixed by the time they arrive. Perhaps if I can just get a technician to move in with me the problems will stay away. |
