US Telco Support > AT&T > AT&T Midwest > [Speed Problem] Slow Connection in Chicago -- Bad line?

[Speed Problem] Slow Connection in Chicago -- Bad line?

That ATTN is off the wall, even on Interleaved

I'm on fastpath with Elite 6.0 in Columbus and have a very clean line with:

144 Current ATTN DR 7648 1164
145 Current SNRM 16.7 19.0
146 Current LATN 27.3 12.5
147 Current SATN 28.3 12.5
148 Current TP 7.3 11.9

reply to jbm326
Interestingly it looks like your synced at the full rate that you pay for. Not sure if that's all the time or just when you checked it to copy the stats onto here.
My mom has a business just south of the loop in Chicago that's been on AT&T DSL for 8 years, paid for 3/512 all this time and the first two years was continuous dropouts and complete failures, two modems later and some rewiring (not to mention a million calls to AT&T) it was finally stable enough to go 6 years without any major complaint but surely was slow with high latency, and with the times changing that speed was finally too little to do much on the internet.

Reason being for the very poor DSL service for us was all due to AT&T not maintaining there lines properly, the connections to the drops to the buildings at the poles were a mess, the drops themselves, and the NID on our building was a big giant mess with spaghetti on the telco side, with faulty modular connectors that caused severe static on the line. Not to mention on the phone you could hear alot of low pitched humming (lots of interference/crosstalk) I don't think distance from the CO was really the issue, we were only 1.5 miles from the CO serving us.

I don't know how long you've lived in the city or where your from originally but just about everyone I know that's been in Chicago for at least a little while knows that AT&T has a terrible reputation here.

We finally made the switch over to Comcast when they offered us a pretty good deal that would be locked in (with contract) for 2 years.
Internet is now impressive, even at peak hours (on busy Halsted st that is. with lots of other cable subs too) and with there phone service I can actually hear people on the phone now.

Now out here in the suburbs AT&T is quite the opposite. DSL is very reliable and the phone service hasn't had any sort of issue in 7 years (since a digger cut the underground cable to the neighborhood while laying fiber for DSL)

reply to jbm326

Re: [Speed Problem] Slow Connection in Chicago -- Bad line?

reply to jbm326
high attenuation and noise margin? yeah something funky is going on probably. Could be intercom system, bad wiring, bad filter, etc.

If you were a member i'd say go ahead and PM me your number and I'd ensure there isn't a provisioning issue....but I can't.
--
My Blog. Because I desperately need the acknowledgement of others.

Tabitha Ann Judd born 10/24: The Judd Family site!

reply to jbm326
I am probably thinking the interleaving might have more to do with it. His attenuation is within tolerances. Based on what he posted I got the following

28.5db upstream=9,500ft (estimated distance)
Max rate calculated=4728-5240kbps
attenuation downstream= low: 43.375 / High: 51.217

again this is just based on what the OP posted. Removal of the interleaved rate may change his attenuation lower/higher in respects. My guess is probably a little lower toward the mid range. Again going solely on what is posted. The low end atteunation assumes fast path of course, and the high end assumes interleaving is involved depending on what profile.
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!

reply to jbm326
Power-cycle your modem and router. See if that helps.

Try a different speed test site.
»speedtest.umflint.edu/
»www.speakeasy.net/speedtest/

Maybe you do have a bad line. Check for packet loss.
Try pinging your ATT gateway with
ping -n 1000 yourGateway
where yourGateway represents the IP of your gateway.
Post only the summary -- not the whole thing.

The purpose is to see if there is a problem locally to you. You
can find your gateway by looking for the information in your router
screens. If you use Windows without a router, ipconfig will
tell you the IP of your gateway.

The thousand pings should take about 17 minutes.

If you do not run a home router/gateway, then you can run the
ipconfig command from a command window to find your Default
Gateway.

If you use a home router/gateway, you want to ping your ATT
gateway rather than your home gateway. The IP of the ATT
gateway will never be 192.168.*.*.

Your ATT gateway address will be listed in your home router pages
somewhere. The upper two bytes/numbers will be the same as your
WAN address. The lowest byte/number will be a 254-- at least it is
for me. . The byte/number next to the lowest will either be the
same as for your WAN, or it could be an even number just a little
lower.

You can also identify your ATT gateway with tracert (Windows), or
traceroute (*nix), in a command window. The first hop that is not
local to your house is your ATT gateway. This would typically be
the second or first hop.

I also recommend the the standard version of Ping Plotter.