High latency at hop to Zone

[Mark0001]

having trouble getting AOL to fix their equipment... here is the trace. as u can see the high latency begins at hop 12 which according to Who Is belongs to AOL who have been impossible to talk to and I have sent several emails to domains@aol.net and got no response. any suggestions or am i reading the trace wrong and should be trying to contact someone else. I have RR and have contacted them and been told they have no control. Oh and this is the only route that is messed up. if i go other places that dont involve this particular hop latency is very good. Any contact numbers or addresses would be of great help

1 14 ms 13 ms <10 ms 10.54.96.1
2 14 ms 14 ms <10 ms srp0-0.hstntxbis-rtr2.houston.rr.com [24.28.96.1
26]
3 14 ms <10 ms <10 ms srp2-0.hstntxeas-rtr1.houston.rr.com [24.28.96.1
]
4 13 ms 28 ms 14 ms 24.28.96.197
5 14 ms 41 ms 14 ms srp8-0.hstntxtid-rtr3.texas.rr.com [24.93.33.147
]
6 14 ms 13 ms 14 ms pop1-hou-P7-2.atdn.net [66.185.136.77]
7 14 ms 14 ms <10 ms bb1-hou-P0-0.atdn.net [66.185.146.97]
8 41 ms 28 ms 41 ms bb1-atm-P7-0.atdn.net [66.185.152.184]
9 41 ms 41 ms 28 ms bb1-cha-P6-0.atdn.net [66.185.152.183]
10 41 ms 42 ms 55 ms bb1-vie-P10-0.atdn.net [66.185.152.29]
11 42 ms 41 ms 41 ms pop1-vie-P4-0.atdn.net [66.185.139.81]
12 343 ms 329 ms 330 ms Microsoft.atdn.net [66.185.139.94]
13 329 ms 343 ms 330 ms gig4-0.core1.was1.us.msn.net [207.46.33.137]
14 330 ms 330 ms 329 ms pos3-0.core2.sea1.us.msn.net [207.46.33.134]
15 329 ms 344 ms 329 ms pos3-0.core1.pao1.us.msn.net [207.46.33.41]
16 343 ms 343 ms 344 ms pos15-0.core1.sea1.us.msn.net [207.46.33.29]
17 344 ms 329 ms 330 ms 207.46.36.66
18 343 ms 343 ms 329 ms 207.46.155.17
19 344 ms 329 ms 343 ms 207.46.129.179
20 343 ms 330 ms 329 ms zone.com [207.46.203.12]

[Kip Patterson]

Hop 12 is the ATDN side of a router that connects ATDN to MSN at MAE East in Vienna, VA. From there, the circuit goes to Seattle et al. The latency should be maybe 90 ms given the number of hops and the distance. I doubt that the problem is in the equipment, it is far more likely to be an overloaded circuit, and it may not be at that point in the loop. It could be anywhere in the return path.

Hard to say whether the router is the responsibility of ATDN or MSN. Doesn't matter, because neither is going to respond to you, sorry to say, Imagine the nerve of someone who thinks a company should talk to them just because he is a customer. What is this world coming to?

Welcome to Speedguide!

Kip

[Mark0001]

your estimate is correct the speed starting at this point has been 80-90 ms and for a while was as low as 55ms. who is says this-- which indicates its an AOL unit--- have sent emails to the address to no avail. has been this way for at least 6 days now (that was when I got on and noticed a problem and actually ran a trace)

OrgName: AOL Transit Data Network
OrgID: ATDN

NetRange: 66.185.128.0 - 66.185.159.255
CIDR: 66.185.128.0/19
NetName: ATDN
NetHandle: NET-66-185-128-0-1
Parent: NET-66-0-0-0-0
NetType: Direct Assignment
NameServer: DNS-01.ATDN.NET
NameServer: DNS-02.ATDN.NET
Comment:
RegDate: 2001-10-31
Updated: 2001-10-31

TechHandle: AOL-NOC-ARIN
TechName: America Online, Inc.
TechPhone: +1-703-265-4670
TechEmail: domains@aol.net

# ARIN Whois database, last updated 2002-10-19 19:05
# Enter ? for additional hints on searching ARIN's Whois database.