rs.internic.net has been unreachable most of today (4/2). Anyone know what's
going on? This is starting to get really annoying.
Eric
We seem to be able to get to them (albeit with some congestion at various
points beyond us):
nwnexus # traceroute rs.internic.net
traceroute to rs.internic.net (198.41.0.6), 30 hops max, 40 byte packets
1 192.135.191.254 (192.135.191.254) 0 ms 4 ms 4 ms
2 border4-serial2-1.Seattle.mci.net (204.70.55.13) 8 ms 23 ms 16 ms
3 core-fddi-1.Seattle.mci.net (204.70.3.145) 8 ms 16 ms 8 ms
4 core2-hssi-3.Denver.mci.net (204.70.1.89) 152 ms 51 ms 258 ms
5 core1-loopback.Denver.mci.net (204.70.4.157) 51 ms 121 ms 141 ms
6 core2-hssi-2.WestOrange.mci.net (204.70.1.110) 102 ms 98 ms 86 ms
7 core1-loopback.WestOrange.mci.net (204.70.4.181) 86 ms 90 ms 125 ms
8 core2-hssi-2.Washington.mci.net (204.70.1.106) 105 ms 121 ms 121 ms
9 core1-aip-4.Washington.mci.net (204.70.1.73) 98 ms 129 ms *
10 border1-fddi-0.Washington.mci.net (204.70.2.2) 145 ms 98 ms 102 ms
11 suranet-wtn-ds3.Washington.mci.net (204.70.56.6) 191 ms 133 ms 113 ms
12 wtn-9.bbnplanet.net (128.167.7.9) 211 ms 82 ms 160 ms
13 * netsol.bbnplanet.net (192.221.63.90) 156 ms 113 ms
14 rs1.internic.net (198.41.0.6) 211 ms 137 ms 94 ms