ettoredjr
join:2006-08-24
Hollywood, FL
| [Line Problem] Latency Issues and Service Drops in Hollywood, FL
I have been experiencing latency issues and service drops in and out for the past 2 months. The problem is especially worse in the evening after 5 pm. I spent an entire evening with AT&T Tech Support to no avail. I am at the point where Comcast is looking good. Here are the last couple of line quality tests:
Today 5/15 »/linequality/8···/2385068
Monday 5/12 »/linequality/7···/2383930 |
|
FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
 ·AT&T Southeast
 ·T-Mobile US
| Re: [Line Problem] Latency Issues and Service Drops in Hollywood
said by ettoredjr  :I have been experiencing latency issues and service drops in and out for the past 2 months. The problem is especially worse in the evening after 5 pm. I spent an entire evening with AT&T Tech Support to no avail. I am at the point where Comcast is looking good. Here are the last couple of line quality tests: Today 5/15 » /linequality/8···/2385068Monday 5/12 » /linequality/7···/2383930 get your modem dsl stats and post them here.
if you don't know how:
»AT&T Southeast Forum FAQ »How do I check modem stats & event logs? What do the numbers mean?
then we can go from there |
|
Press2Esc
join:2005-07-03
US
·AT&T Southeast
| Per Ettoredjr's stats in S.FL, 70.151.243.78 (3x) , 65.83.238.189, & 65.14.255.126 are all Bellsouth routers with high packet loss. FastAttack's in Lauderdale, is also lists 70.151.243.78 (3x), 65.83.238.189 & 65.14.255.126 as faulty routers.
Hmmm, am I just physic or does anyone notice a pattern??? I am in awe that Bellsouth does not pay closer attention to their routers. Also, IMHO, their routing tables used to push out packets outside their network is possibly even more rediculous. |
|
FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
·AT&T Southeast
·T-Mobile US
| said by Press2Esc :Per Ettoredjr's stats in S.FL, 70.151.243.78 (3x) , 65.83.238.189, & 65.14.255.126 are all Bellsouth routers with high packet loss. FastAttack's in Lauderdale, is also lists 70.151.243.78 (3x), 65.83.238.189 & 65.14.255.126 as faulty routers. Hmmm, am I just physic or does anyone notice a pattern??? I am in awe that Bellsouth does not pay closer attention to their routers. Also, IMHO, their routing tables used to push out packets outside their network is possibly even more rediculous. I sure don't see this so called pattern, I have previous line quality tests and the only packet loss is in the side of cogentco... and their handoffs on a tier 3 backhaul, which is not surprising to see packet loss.
»/linequality/nil/2386172 |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to Press2Esc
The interesting router is this one:
Would this be the aggregation router?
From:
»/linequality/nil/2368816
I gather that my aggregation router is 'adsl-69-110-149-81.dsl.pltn13.pacbell.net'.
Any hops after this one don't count; not until this one is fixed, anyway.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Airwolf7
Premium
join:2004-12-12
Franklin, KY | Norman, Why does your look all messed up.
»/linequality/nil/2386195 |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| I just picked it from my list to demonstrate what I assume is the aggregation router. I didn't think it was "messed up". I certainly wasn't having any trouble with the connection.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Press2Esc
join:2005-07-03
US
·AT&T Southeast
| reply to FastAttack
FA, you seriously don't see anything wrong??
cogentco.com 0% loss
quest.net 0% loss
att.net 0% loss
70.151.243.78 52% Loss
65.83.238.189 15% loss
70.151.243.78 44% Loss
te3-1.ccr01.atl01.atlas.cogentco.com - 7% loss
quest.net 0% loss
att.net 0% loss
ixc00rdu-7-0.bellsouth.net 17% loss
70.151.243.78 55% Loss
65.83.238.189 9% loss
65.14.255.126 50% loss
cogentco.com 0% loss
ixc00rdu-7-0.bellsouth.net 9% loss
70.151.243.78 52% Loss
quest.net 0% loss
att.net 0% loss
65.83.238.189 15% loss
70.151.243.78 44% Loss
cogentco.com 7% loss
ixc00rdu-7-0.bellsouth.net 17% loss
70.151.243.78 55% Loss
65.83.238.189 9% loss
65.14.255.126 50% loss
Check out the (pink) color-coded lines, which by design are supposed to highlight the problem routers... Now, step back and notice that ALL other non-Bellsouth routers (AT&T, Quest, Cognetco) do not have a problem.
By defintion, a router w/50% packet loss translates to a 50% chance a small (40Byte?) packet will get through the problem (aka Black Hole) router... If the router has a problem with a rediculously small packet, albeit a "normal" (1500B) packet travelling at 100Mb or 1Gb will have even more difficulty getting through the router. See for yourself - "ping -l 1490 70.151.243.78".
Again my real issue is router admin... Until the problem with that router is resolved, Ettoredjr and many, many others (including you) in the area, will experience dropped packets.
P2E |
|
Press2Esc
join:2005-07-03
US | reply to NormanS
Norm, I am not sure of the router functions as an edge router - it barely functions as a router - period.
Also, if I am understanding your graphic - I dont believe the reverse DNS is an issue when using an IP address.
P2E |
|
FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
·AT&T Southeast
·T-Mobile US
| reply to Press2Esc
said by Press2Esc :FA, you seriously don't see anything wrong?? cogentco.com 0% loss quest.net 0% loss att.net 0% loss 70.151.243.78 52% Loss 65.83.238.189 15% loss 70.151.243.78 44% Loss te3-1.ccr01.atl01.atlas.cogentco.com - 7% loss quest.net 0% loss att.net 0% loss ixc00rdu-7-0.bellsouth.net 17% loss 70.151.243.78 55% Loss 65.83.238.189 9% loss 65.14.255.126 50% loss cogentco.com 0% loss ixc00rdu-7-0.bellsouth.net 9% loss 70.151.243.78 52% Loss quest.net 0% loss att.net 0% loss 65.83.238.189 15% loss 70.151.243.78 44% Loss cogentco.com 7% loss ixc00rdu-7-0.bellsouth.net 17% loss 70.151.243.78 55% Loss 65.83.238.189 9% loss 65.14.255.126 50% loss Check out the (pink) color-coded lines, which by design are supposed to highlight the problem routers... Now, step back and notice that ALL other non-Bellsouth routers (AT&T, Quest, Cognetco) do not have a problem. By defintion, a router w/50% packet loss translates to a 50% chance a small (40Byte?) packet will get through the problem (aka Black Hole) router... If the router has a problem with a rediculously small packet, albeit a "normal" (1500B) packet travelling at 100Mb or 1Gb will have even more difficulty getting through the router. See for yourself - "ping -l 1490 70.151.243.78". Again my real issue is router admin... Until the problem with that router is resolved, Ettoredjr and many, many others (including you) in the area, will experience dropped packets. P2E No I don't , i see the ops line testing being off , but i just showed you that on my end everything is fine and dandy other than congentco doing the bad handoff and showing the packet loss.. |
|
Airwolf7
Premium
join:2004-12-12
Franklin, KY
·AT&T Southeast
edit:
May 19th, @05:56PM
| reply to NormanS
Norman, I was just looking at the pretty pictures.
I was just wondering why your graphs had the green, yellow, and red bars stacked next to each other like the signal meter on a cell phone.
It looked like one of those old Cingular commercials with the five bars of service.
I ran a test just to see what mine looked like and it was all green and even across the top and I wondered why yours looked so different. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
edit:
May 19th, @05:29PM
| reply to Press2Esc
Sorry, I didn't mean to mislead you. It was the IP address that I found interesting, not the lack of rDNS. My understanding of "the way things work" is that this is the first hop showing packet loss, ergo, this router, not the downstream routers, is the source of the problem. I don't know if this is a sign of congestion, or what.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to Airwolf7
Could have been that I had a torrent underway when I ran that test. At the time I wasn't looking for low latency, just so-called "packet loss" on the intermediary routers. It looks like the gold and red bars related to high latency.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Press2Esc
join:2005-07-03
US | Good point Norman.. Torrents & trojans have been known to flood the ISPs router that connects the DSL customers to their network. P2E |
|
DslDeprived
@comcast.net
| reply to ettoredjr
> I am at the point where Comcast is looking good.
Don't do it! I live in Pembroke Pines (behind the mall), and Comcast has been awful ever since I moved into my new house and was forced to get service from them because AT&T doesn't have any available DSL ports in my neighborhood. I've had AT LEAST one hour+ outage per week (that was ultimately confirmed to affect at least one other user in my neighborhood), and the past week has been excruciatingly bad, with daily outages long enough to notice. I've burned at least a half hour of cellular airtime calling them to report outages over the past month (no internet == no VoIP phone).
Right now I'd KILL to be able to enjoy having DSL again. Comcast internet is about twice as fast as 3mbit DSL, with comparable latency, when it works... but so far, I've had more hours of downtime in ~6 weeks with Comcast than I had in EIGHT YEARS with DSL.
That said, if you currently have 3.0/384 service, you might want to consider switching to SnappyDSL. BellSouth/AT&T won't allow them to offer 6.0M service, but they're AWESOME about tracking down problems and riding BellSouth/AT&T's a$$ to get them fixed immediately when/if they happen, and do their very best to provide as close to 100% availability as they can. They're more expensive than FastAccess, but IMHO they're worth every penny, and work hard to earn it daily. They're probably 90% of the reason why I'm so miserable with Comcast now... they bent over backwards to make me happy, and set my expectations to a level Comcast can't/won't satisfy.
In retrospect, I totally took Snappy for granted, and had no idea how awful life in the "outside world" could possibly be. If it's not obvious, I miss them badly  |
|
Press2Esc
join:2005-07-03
US
·AT&T Southeast
| DSL'D, I would recommend you install a bandwidth monitor program and verify your LAN or WAN bandwidth is not being adversely consumed. If so, ID the source of the problem and block the respective domain or IP traffic.
Also, if your LAN or a connected PC has been "attached", changing over to cable to another ISP, may not resolve anything..
P2E |
|
