Extended maintenance report from carrier.

Fri Sep 12 08:11:32 PDT 2003 — Extended maintenance report from carrier. One of our providers has been performing maintenance that has lasted longer than their expect window. Our redundant connections via multiple carriers and transport providers has insulated us from a service affecting situation. -Operations

New Microsoft RPC vulnerability.

Wed Sep 10 18:10:10 PDT 2003 — New Microsoft RPC vulnerability. Microsoft announced today a new vulnerability in Windows NT, 2000, XP and others that is very similar to the security flaw that the Blaster worm used. Patches for this new flaw have been released and are available at Windows Update ( windowsupdate.microsoft.com ) and we urge our customers to patch their systems immediately. — Eli, Support

Web Server Instability: Over the past few…

Wed Sep 10 14:11:04 PDT 2003 — Web Server Instability: Over the past few days we have been seeing some instability in our webserver cluster that has been resulting in periodic slow downs or refused connections. We have disabled a suspect user cgi that appears to have been accidentally DoSing the servers. -Sonic Operations

Barham tower outage continues.

Thu Sep 4 12:24:15 PDT 2003 — Barham tower outage continues. Broadlink’s Barham tower is still out of service; technicians are working on the problem and Broadlink expects to have service restored late this afternoon. -Sonic.net and Broadlink Operations

UPDATE 17:12:25 PDT 2003: Broadlink technicians are still working on the damaged tower; service has not been restored. We will post an update here as soon as we have more information. -Sonic.net and Broadlink Operations

Barham tower back in service.

Thu Sep 4 19:38:05 PDT 2003 — Barham tower back in service. Broadlink was able to replace the last of the damaged equipment this afternoon, later than expected because the damage was more severe than initial inspection showed. Testing was carried out this early evening and there should be no further issues. -Sonic.net and Broadlink Operations

Power outage in San Francisco.

Wed Sep 3 10:22:36 PDT 2003 — Power outage in San Francisco. A power switching error this morning at one of our San Francisco facilities caused a short outage of all services at that location. This included all dialup lines whose number ends in 3, eg., 707-522-1003. Power has been restored and there should be no further problems. -Kelsey, Nathan and John

Storm outage on Broadlink’s Barham tower.

Wed Sep 3 09:27:02 PDT 2003 — Storm outage on Broadlink’s Barham tower. It appears the thunderstorm that rolled through the Santa Rosa area this morning has caused a problem with Broadlink’s Barham tower. This has resulted in some Broadlink outages. PG&E can not “confirm nor deny” power problems to the site. A Broadlink engineer is one his way to the tower. -Scott, tech support, and Broadlink

522-1003 and other numbers served by our one…

Wed Sep 3 20:45:18 PDT 2003 — 522-1003 and other numbers served by our one of our San Francisco POPs have been Intermittently returning all circuits are busy messages since earlier this evening. This is a failure due to a failure on one of the eight router cards which handles three of PRI’s of modems. We are working to resolve the problem and hope to have it resolved shortly. -Operations

Mail.sonic.net MX record removed.

Tue Sep 2 15:26:43 PDT 2003 — Mail.sonic.net MX record removed. Last week, in an attempt to compensate for some broken email clients, we put an MX record for mail.sonic.net pointing at mx.sonic.net. This apparently broke sendmail “smarthosting” for some of our customers. We have now removed that MX record. Customers are reminded that “customer@mail.sonic.net” is not a valid return address to include in email. Please check your configuration. -Operations

Dialup authentication failing.

Tue Sep 2 14:52:57 PDT 2003 — Dialup authentication failing. The authentication process for dialup users has failed. We are switching all of our dialup servers to new authentication servers and they are gradually returning to service. We expect them to all be working by 3 PM today. -Russ, Nathan and John

Update: This problem is resolved as of 3:20 PM.