Month: September 2000

Sun Sep 3 01:43:54 PDT 2000 — Earthquake. That was a 5.2 earthquake epicentered 3 miles WSW of Yountville. More information can be found at the USGS: quake.wr.usgs.gov/recenteqs/Maps/123-39.html Aftershock prediction information for this quake can be found at quake.wr.usgs.gov/recenteqs/QuakeAddons/nc51101203.afterwarn.html And finally, you can file a “Did You Feel It?” report with the Community Internet intensity map here:

pasadena.wr.usgs.gov/shake/STORE/X51101203/ciim_form.html (You may want to wait a bit on that last link, as it appears to be impacted by other earthquake-feelers.) -Scott, Nathan, and Mitch

Sat Sep 2 16:59:19 PDT 2000 — SOLVED: High latency and packet loss on UUNet in San Francisco. As of 16:43 PDT, the high latency and packet loss on UUNet’s network in San Francisco has cleared. Our new Internet monitoring tool — “see” — detected the problem while monitoring the path from here to www.ora.com. Since most of our traffic to the Internet did not travel over the latent path, we didn’t expect customers to notice the problem (unless they were visiting www.ora.com, of course) — and from talking with Sonic.net tech support, it appears we received no calls about the problem. Here “see” has fulfilled its role of notifying us about potential problems before you, our customer, notice them. -Scott

Sat Sep 2 14:51:29 PDT 2000 — High latency and packet loss on UUNet in San Francisco. Our new Internet monitoring tool — “see” — has detected unacceptable latency and packet loss on UUNet’s network in San Francisco. Upon contacting UUNet, they informed us that they already have a ticket open on the problem. “See” detected the problem as part of its monitoring of the path from here to www.ora.com. Since most of our traffic to the Internet does not travel over the latent path, we don’t expect customers to notice the problem (unless you are visiting www.ora.com, of course). Here, “see” has fulfilled its role of notifying us about potential problems before you, the customer, notice them. -Scott

Fri Sep 1 08:35:03 PDT 2000 — One of our redundant mail servers lost contact with our authentication server, this would have caused some people to get an invalid password error when checking mail. This was discovered quickly and fixed. -Steve