Adelphia......Again... :(

Anyone else feeling the pain?

Im getting about ~200ms anywhere I go. Ive been on phone and IM with these level 1 techs for far too long trying to explain how a ping and traceroute works. Anyone else had any luck with Adelphia?

[root@localhost ~]# traceroute yahoo.com
traceroute: Warning: yahoo.com has multiple addresses; using 216.109.112.135
traceroute to yahoo.com (216.109.112.135), 30 hops max, 38 byte packets
1 10.0.0.1 (10.0.0.1) 0.321 ms 0.304 ms 0.248 ms
2 10.10.96.1 (10.10.96.1) 8.143 ms 13.567 ms 9.667 ms
3 68.171.67.253 (68.171.67.253) 8.077 ms 10.324 ms 9.504 ms
4 68.171.67.113 (68.171.67.113) 9.084 ms 10.326 ms 9.580 ms
5 * a2-00-00-00.a0.dca91.adelphiacom.net (66.109.15.169) 160.662 ms 134.936 ms
6 ae-0-0.c1.dca91.twc-core.net (66.109.1.137) 158.052 ms ae-0-0.c0.dca91.twc-core.net (66.109.1.129) 130.042 ms 131.373 ms
7 ae-1-0.p1.dca91.twc-core.net (66.109.1.190) 129.703 ms ae-0-0.p1.dca91.twc-core.net (66.109.1.186) 164.916 ms ae-1-0.p1.dca91.twc-core.net (66.109.1.190) 153.807 ms
8 unk-426d0b4a.adelphiacom.net (66.109.11.74) 163.884 ms 163.171 ms 122.114 ms
9 ge-0-0-0-p111.msr2.dcn.yahoo.com (216.115.108.7) 161.733 ms ge-1-0-0-p101.msr1.dcn.yahoo.com (216.115.108.43) 134.148 ms ge-1-0-0-p111.msr2.dcn.yahoo.com (216.115.108.47) 157.553 ms



between hop 4 and 5 is my pain. Ive seen this problem for over a month w/no solution.

I want FIOS!

 

5 * a2-00-00-00.a0.dca91.adelphiacom.net (66.109.15.169) 160.662 ms 134.936 ms

This is most likely Adelphia's Router/Firewall in their DCA Hub, it then hops to the Time Warner (AOL) backbone...it could also be a routing table issue with Adelphia...depending on the traffic and load balance, your IP maybe "the last one in" slowing down your speed and roundtrip MS.

Also here is a GREAT article on Verizon Fios....

http://www.eweek.com/article2/0,1895,1984353,00.asp

 

Its more than likely circuit overutilization or a horrible attempt at traffic loadbalancing via BGP. Based on the DNS reverse lookup on those IP addresses, it looks as if the Time Warner portion of the network was "plugged" in w/out any network engineering...... and they ask me why I drink.

 

Jonnie, Jack and Jim have become my very close friends....since broadband companies have a 250/1 ratio and "hot potato" long haul traffic, just to put it back on their network. I could tell you crazy stories of my NOC days...but it could be a bit racy for this venue FWIW...it's great to dialogue with someone like yourself who has a clear understanding of networks

 

Is that anything like Abraham, Martin, and John.....?

 

...maybe, that is if I am on my knees praying to the "white throne" after speeding too much time with my three boys (jonnie, jack and jim)

 

Just to clarify its Time Warner Cable network (not the AOL network) that is having the slowness. My guess is Adelphia is starting to move traffic over to Time Warner and Comcast backbone in anticipation of the Time Warner Cable/Comcast cutover.

 

Visit DSL Reports for the full story:

http://www.dslreports.com/forum/remark,16805392~days=9999



Exec summary: the issue is affecting people all over VA, WV, and MD...and relates to the integration of the TW and Adelphia networks. Level 1 Adelphia tech support normally feigns ignorance, but you can reach folks inside Adelphia/TW who will acknowledge the issue...and issue daily credits...but they will not provide an estimated time for repair...which is the ETR acronym that you will see folks throwing around on that site.

 

Thanks Steve, Im calling to get 4 weeks of credit. I opened a ticket over 4 weeks ago and the problem is still here. Grrrrrrr.

 

FWIW ... I thought that the Loudoun Adelphia system was going to Comcast .. in which case, what does the Adelphia/Time Warner stuff have to do with that ??

 

While Loudoun County is getting Comcast for their primary provider, there are probably portions of the backbone that might travel between both Comcast and Time Warner during this initial cutover phase.

 

Interesting ... where's the nearest TW network ??

 

Woohoo, it's really cooking tonight:

Last Result:
Download Speed: 508 kbps (63.5 KB/sec transfer rate)
Upload Speed: 215 kbps (26.9 KB/sec transfer rate)

 

Interesting question...but TW is somehow in the mix at more than just a network level, because I sent email to support@adelphia.com and got a response from supportdst@twcable.com ...and the automated email stated:


Dear Valued Customer,

This is an automated response from Time Warner Cable Customer Care.

You will receive a personal response via Email from one of our Customer Support Representatives, as soon as we have researched your account.

Until the transition from Adelphia to Time Warner Cable is completed, please visit Adelphia.net to find answers and solutions to many questions you may have.

 

WHOA ... that definitely got misrouted .. unless the regions got changed since I left. I thought that since there were no TWC regions in the area, the Loudoun Adelphia cable region was going to Comcast ! What changed ??

 

The TWC GNOC, customer care and commercial services is located in Herndon, however from what I have heard Loudoun is going to Comcast. Not sure about the routing issues. I'll ask around and see what I can find.

 

I was talking to someone at Adelphia today and the comcast change over is expected to be completed by the end of october if all goes well. So expect problems for a little while longer.

Lee J Buividas

 

I got a full months credit. Took 5 minutes to convince them . Id still rather have a connection with less latency than dialup than to have the credit.....

 

I spoke with TWC network ops folks and they are looking into it. There are a few of them living with Adephia and are having the same issues.

The TWC routers you see in the traceroutes are, according to them, renamed adelphia assets. From my understanding all Adelphia network assets became the property of TWC and Comcast will utilize them in the markets they now control through peering arrangements.

They also said that Adelphia had not spent any capital on network upgrades for the past 8 months for the pending acquisition. It will probably take some time to correct with the transitions in full swing, but my traceroutes last night showed pretty decent response times and progressively got worse during the peak periods. They will probably require some expansion.

 

Should be better in a couple of days. They found a network component that is at capacity. An upgrade is already in the works.