It actually looked like it was farther in the att network, after cw's peer the next hop after cw's peer. I just tried the trace again and it seems better. Cw seems to be handing off to att at a different point in santaclara now not sanfrancisco which seemed to help. Again though it looked like att was the issue because cw looked fine up tntil one hop after cw ended. On Wed, 12 Mar 2003, IP-GNOC wrote:
No issues to report, probably a return path issue. It'd be easier to confirm that with a traceroute showing the latency. And you will get a timely response from noc@cw.net, which is where this email belongs.
Regards, Mark Kasten Cable & Wireless
Scott Granados wrote:
Anyone else seeing an issue between cw and att somewhere near sf it looks like.
I go from 4 ms, at the point tagged as the peer between cw and att and 1400 ms once I land on att.
THanks