hescominsoon
join:2003-02-18
Brunswick, MD
 ·Comcast
 ·Verizon Online DSL
| Garland Problems? It appears the ice storm has taken my mom's service in Garland tx down. She cannot ping her gateway form there and i cannot get past the dallas router on a tracert. Any Attbi techs have any ideas about what is going on?
--
God Blesshttp://www.faithwalk.org | |
|
 yellow_cloud
join:2001-06-23
Plano, TX | Re: Garland Problems? Plano here. Very slow download. That is the third time so far for the year. | |
|
usualpulp
join:2001-03-08
Dallas, TX | im in the plano/carrollton area, technically dallas....but my connection has been fine all day 1700ish down and around 256 up | |
|
tswierk
@attbi.com
| My connections in Plano have been horrible the past few days. Consistently seeing 300/322 (yes you read that right, faster upload than download). Time to give support a call I suppose. My connections have consistently been 1700/270s up until this past week or so.
Todd | |
|
troublehere2
@attbi.com | i'm getting spikes here...it's fast in patches but ultra slow for the most part..clocking 200 kbps on newsgroups | |
|
tswierk
@attbi.com
| Well I did the online chat thing tonight and they say that my connection speeds look excellent... I used to consistently get 1700/275 but yesterday & today I am getting 200-300/300-400 on dslreports speed test. I'll give it one more day before calling them (and probably getting a truck roll).
Todd | |
|
yellow_cloud
join:2001-06-23
Plano, TX | I did not call attbi, but my download speed is back to normal of 1.7 Mbps this morning.
Thanks. | |
|
 | 
ramell
join:2002-02-12
Carrollton, TX | Re: Garland Problems? Carrollton here...and its been intermittent quality of service...
sometimes 1700's dload/140's upload
sometimes 400-800 dloads/ 100's dload | |
|
CrazyLEG
join:2002-06-13
Richardson, TX
| I'm in the Plano/Richardson Area. And my ping times are not bad, but it's getting bad, plus I'm getting TONS of Packet Loss.
I ran Ping Plotter last night and I'm good up until At&t's Router then I get 30-50% PL.
It's frustrating to say the least. | |
|
yellow_cloud
join:2001-06-23
Plano, TX | In the water again. 0.3 Mbps download. Sigh!
3 times in two months, each time lasts for 2-3 days. Sigh!
And they want a raise. Sigh! | |
|
| EndLoser
join:2001-12-29
Richardson, TX
|  Re: Garland Problems?
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. | |
|
|
|
|
