BBN outage

[In the message entitled "Re: BBN outage" on Oct 11, 17:23, Matthew Kaufman writes:]

You'd think us network-operators would learn from these past several
big outages and have a good, reliable, mailing list up by now, but
I haven't heard about one. I'm reluctant to start it myself, because I
don't have enough network paths out of here to make it useful during
a serious multi-provider problem.

I will be happy to create this. In fact, it is done.

outage@bungi.com is the address, outage-request@bungi.com for
subscription. Majordomo-run, so it should be pretty painless.

Ready now.

Rather than creating multiple lists, you might want to subscribe to the
list that Stan Barber created. The list is 'outage-discuss@academ.com'
and you can subcribe with a subscribe message to
'outage-discuss-request@academ.com'

Additionally, ISPs wishing to share outage information should look at

  http://compute.merit.edu/ipn.html

or send mail to 'outage@ra.net' for information on the Inter-Provider
Notification project being coordinated by Craig Labovitz.

-jh-

I think that maybe the list should be at someplace that is a little better
connected.

traceroute to www.bungi.com (207.126.97.5), 30 hops max, 40 byte packets
1 cyber-gw.cyberbot.com (205.215.47.1) 1.517 ms 1.453 ms 1.516 ms
2 ts-arl-2.netrail.net (205.215.6.101) 36.702 ms 34.47 ms 34.895 ms
3 E1-10M.nr-1-Arlington-VA.netrail.net (205.215.6.1) 35.333 ms 36.732
ms 34.557 ms
4 E0-10M.nr-2-Arlington-VA.netrail.net (205.215.4.2) 36.843 ms 37.83
ms 37.579 ms
5 mae-east.good.net (192.41.177.101) 39.82 ms 38.008 ms 42.199 ms
6 san-jose.good.net (207.98.128.2) 105.617 ms 107.759 ms 107.045 ms
7 abovenet-10mbps.san-jose.good.net (207.98.191.130) 113.171 ms
108.493 ms 108.49 ms
8 San-Jose-1-T3.above.net (207.126.96.246) 318.117 ms 266.789 ms
347.158 ms
9 San-Jose-2-T1.above.net (207.126.96.250) 295.321 ms 318.647 ms
306.12 ms
10 min.bungi.com (207.126.97.5) 112.304 ms 204.586 ms 207.763 ms

Nathan Stratton CEO, NetRail, Inc. Tracking the future today!