Chris, You need to provide traceroutes from both directions. The below is for Dallas --> Denver, but the return path (Denver --> Dallas) needs to be provided too. You might find that the return path goes through some provider other than Zayo/360/Abovenet/whateverthey'recalledtoday. I know that's hard to do when the path has latency or packet loss (which you don't show in your results -- you only show latency), but this is exactly what a cronjob traceroute writing to a log file is for. :-) My point: remember that routing on the Internet most of the time is asymmetric. Reference material (read, do not skim): http://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N4... Finally, you didn't provide IP addresses of either server (in Denver or Dallas), so when you ask for "someone else to test", that's not easily doable, at least not to the endpoints involved (pinging routers is not sufficient evidence, sadly). -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Thu, Dec 13, 2012 at 11:10:32PM -0500, chris wrote:
Seeing massive packet loss and high latency from 360.net (which appears to be owned by zayo/abovenet/whatever) in denver....
Here is a trace snip from our server @ softlayer in dallas to one of our servers in denver
5: ae0.bbr01.cs01.lax01.networklayer.com (173.192.18.141) 29.698ms 6: no reply 7: 66.62.2.213 (66.62.2.213) 4588.320ms 8: den1-core-01-xe-1-1-0.360.net (66.62.2.166) 22583.831ms
I only have one one server in denver that I can reproduce this with hoping someone can else can test and reproduce similar issues
thanks chris
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages