|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Severe Response Degradation
This is what we are currently seeing. Unfortunately @Home does not do reverse dns for their routers so I am going by their helpdesk's descriptions of locations. I do know that the router is in SF but could not get an exact location due to @home claiming it to be a sprint issue. This also brings back the conversation of RFC1918 addressing and the problems it can cause when troubleshooting response issues. Since opening the ticket the response times are starting to get better (less actual timeouts) but the normal ping of 30-40ms is definitely not there and does severely suffer when more data intensive packets head that way. I still am not sure about locations as @home does not publish any connectivity maps that I have been able to get a hold of. From my traceroutes I would point directly to @Home's router but do not have the ability hold them to this fact which then makes it difficult when I go back and ask for allowances for bad service on my circuits. Tracing route to www.news.com [204.162.80.176] over a maximum of 30 hops: 3 <10 ms 10 ms <10 ms 10.252.25.37 4 <10 ms 10 ms <10 ms 10.252.32.1 5 141 ms 170 ms 170 ms 172.16.2.161 @Home locates this router in SF as a Peer to Sprint 6 160 ms 180 ms 181 ms mae-west.att.net [198.32.136.124] 7 190 ms 180 ms 191 ms gr1-h30.sffca.ip.att.net [192.205.31.41] 8 190 ms 180 ms 171 ms 12.127.1.193 9 140 ms 151 ms 160 ms ar2-a300s1.sffca.ip.att.net [12.127.1.141] 10 111 ms 120 ms 110 ms 12.127.194.46 11 * 12.127.194.46 reports: Destination net unreachable. Tracing route to www.yahoo.com [204.71.200.75] over a maximum of 30 hops: 3 <10 ms 10 ms <10 ms 10.252.25.37 4 <10 ms 10 ms <10 ms 10.252.32.1 5 170 ms 160 ms 140 ms 172.16.3.205 @Home locates this router in SF as a Peer to Sprint 6 150 ms 170 ms 160 ms 206.251.7.201 7 141 ms 150 ms 140 ms 206.251.7.43 8 90 ms 121 ms 120 ms 204.71.200.75 Trace complete. Derrick Bennett Quoted from Stephen: Not that the problem doesn't exist, but ... Sprint does not have a router (or any presence whatsoever) at PAIX. If anyone at PAIX peers with Sprint from a router located at PAIX, they must be buying a circuit to a Sprint POP to do it. Since Sprint has no presence at PAIX, what do you mean by "affects many of the Sprint Net peers in PAIX?" Do you have a traceroute to support your assertion that the @Home router in question is located at PAIX? (I don't know whether it is or no, but none of the traceroutes into @Home that I do from my PAIX routers show an @Home router numbered in 172.16.6 as a next hop.) If there is a problem such as you describe, it's not affecting the two PAIX routers I have that peer with @Home. Stephen
|