26 Apr
2012
26 Apr
'12
5:06 p.m.
We're seeing major routing issues in Los Angeles with peering from HE.net <-> Above.net, specifically after mpr1.lax2.us.above.net. Above.net's looking glass in LA shows traces dying right after he.net, 1 xe-0-1-0.cr2.lax112.us.above.net (64.125.30.250) 0.780 ms 0.571 ms 0.479 ms 2 xe-8-0-0.mpr1.lax12.us.above.net (64.125.30.30) 0.393 ms 0.483 ms 0.404 ms 3 10gigabitethernet1-3.core1.lax1.he.net (206.223.123.37) 0.884 ms 4.619 ms 1.100 ms 4 * * * Both sides seem to be blaming the other. Is anyone routing via above.net or he.net seeing similar issues out west? Best Regards, Erik Soroka Tier III System Administrator InMotion Hosting, Inc. eriks@inmotionhosting.com