aarong3
join:2002-08-01
Los Angeles, CA
| LAX routing issues
the network status page alludes to a core router upgrade about three hours ago today, but I just got home and I'm experiencing some pretty freaky routing issues right now.
traceroute genmay.net
traceroute to genmay.net (207.44.240.22), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.978 ms 0.952 ms 1.855 ms
2 ip-64-32-182-1.dsl.lax.megapath.net (64.32.182.1) 26.261 ms 26.651 ms 31.917 ms
3 fe0-3-0.bbsr1.lax.megapath.net (66.80.131.13) 29.649 ms 30.555 ms 27.906 ms
4 fe2-0.rbak2.lax.megapath.net (66.80.131.10) 30.346 ms 58.547 ms 29.683 ms
5 fe0-3-1.bbsr1.lax.megapath.net (66.80.131.17) 34.389 ms 40.885 ms 29.211 ms
6 fe2-0.rbak2.lax.megapath.net (66.80.131.10) 29.756 ms 27.222 ms 29.108 ms
7 fe0-3-1.bbsr1.lax.megapath.net (66.80.131.17) 28.835 ms 28.501 ms 27.786 ms
8 fe2-0.rbak2.lax.megapath.net (66.80.131.10) 30.157 ms 34.367 ms 30.481 ms
9 fe0-3-1.bbsr1.lax.megapath.net (66.80.131.17) 31.319 ms 37.754 ms 31.711 ms
10 fe2-0.rbak2.lax.megapath.net (66.80.131.10) 43.771 ms 26.734 ms 27.793 ms
11 * * fe0-3-1.bbsr1.lax.megapath.net (66.80.131.17) 29.703 ms
12 fe2-0.rbak2.lax.megapath.net (66.80.131.10) 30.455 ms 31.729 ms 28.042 ms
the packets keep getting bounced between 66.80.131.17 and 66.80.131.10 indefinitely. this happens for genmay.net and deadly.org. however I dont have an issue with dslreports (obviously), slashdot, msn.com, postgresql.org or the majority of other sites out there.
whats the deal? |
