Month: July 1997

Our MCI T1 was offline for five hours this AM

Mon Jul 21 13:58:26 PDT 1997 — Our MCI T1 was offline for five hours this AM between about 8:40am and 1:40pm PST. As we’re a ‘non default’ ISP who is fully multihomed to multiple backbone providers, this didn’t affect our ability to communicate with the rest of the Internet. Our investment in Cisco equipment pays off at times like this. -Dane

A number of bad things are happening out…

Fri Jul 18 17:02:52 PDT 1997 — A number of bad things are happening out there in Internet land. UUNet’s fiber carrier has had a large trunk cut in Wisconson, and this is affecting much of UUNet’s non Bay Area destinations. We’ve been noticing slow access and lots of packet loss. In addition, our network is currently under attack, apparently from another UUNet customer. We’ve blocked access from their network, and we’re working with UUNet security to isolate the source of the attack.

Update on Internic — some root name servers…

Thu Jul 17 07:16:26 PDT 1997 — Update on Internic — some root name servers are still serving incorrect information. We’ve stopped talking to B, E, F, and G.root-servers.net until they get straightened out. (A, C, D, H, and I.root-servers.net seem to be okay.) -Scott

Internic blew their root-domain update, which

Thu Jul 17 03:30:23 PDT 1997 — Internic blew their root-domain update, which means some domains will produce ‘no such host or domain’ errors. (They did the same thing last week too, grrr…). The problem should be corrected within an hour, but I thought the ‘night owls’ would like to know what’s up… -Scott

More minor troubles – power fluctuations…

Wed Jul 16 00:34:46 PDT 1997 — More minor troubles – power fluctuations caused problems with one of the disk arrays connected to our main administration and authentication box, and it had to be rebooted. This may have caused some things like DNS to act a bit slow, but backup auth and DNS should have kept most users functioning well. If you only have one nameserver setup, you may wish to add another in case of trouble like this. I’ve move the array to the new monster UPS. -Dane

Our UUNet T3’s routing session has reset…

Tue Jul 15 23:45:38 PDT 1997 — Our UUNet T3’s routing session has reset itself twice in the past 25 minutes, and the router has been working hard to keep things smooth using the redundant link to MCI. During these changes to the routing, you may notice pauses or inconsistent network performance to sites which would normally use the UUNet connection. I’ve spoken with UUNet, and they don’t show any trouble originating from their end, so we’re keeping an eye on things here. -Dane