Sat Jun 20 18:01:28 PDT 1998 — Tomorrow morning (Sunday 21st), between 12am and 3am, we will be moving some of our backbone equipment into the newly expanded machine room. The only noticable impact should be moving our core router, which will result in approximately 10 minutes downtime. We expect to perform that move between between 2 and 3am. -Scott and Dane

Update – the move is complete, and it went very smoothly. Total downtime while we moved the core router was under 10 minutes at 3:35AM PST. We migrated our six data T1 circuits and two T3 circuits into the new datacenter, and also moved their connections to our new Extreme Networks Gigaswitch. More servers will be migrated into this facility and into this new core network switch in the next couple weeks. -Dane, Scott and Dustin

Fri Jun 19 18:15:42 PDT 1998 — We’re pleased to announce the deployment of our new San Rafael POP! Users in San Rafael and Novato can now reach Sonic as a local call. We’re offering standard analog v.34 connections in this POP, plus K56Flex, v.90 and ISDN. In addition, we’re now offering dedicated Centrex ISDN, T1 and fractional T1 to the San Rafael area. If you’re interested in any of these dedicated services, do let us know. The new San Rafael access number is 415-492-9867. Please dial zero and ask for rate information to make sure that this is a local non-toll call for you if you’re like to use this POP. -Dane, Eric and crew

Sat Jun 13 23:21:45 PDT 1998 — Because of ongoing intermittant problems with nas21.sonic.net (which serves 522-1003), we’ve flashed it to a different firmware version. USR claims that this new engineering release will fix the odd troubles that we’ve had with the equipment’s operating system. When it failed, we had problems with long FTP transfers and with network routing.

Update – the new engineering release would not allow users to authenticate, so we were forced to back up to the previous release of the OS. This leaves us with the intermittant FTP and routing issues. If you notice problems, let us know and we’ll reboot the device, meanwhile we’ve asked the USR support list for advice. -Dane

Update (Mon Jun 15 18:43:31 PDT 1998) – We’ve managed to get the engineering release to load, and the device seems to be a bit more stable. Hopefully this will end troubles with 522-1003! -Dane and Brian

Wed Jun 10 12:50:20 PDT 1998 — Our web server has some minor filesystem corruption on its root filesystem, and it’s currently offline for filesystem repair. We expect to have the server back online in a few minutes. Thanks for your patience. -Dane and Scott (12:55 or so — fixed and back online 🙂 -Scott and Dane

Sun Jun 7 18:56:17 PDT 1998 — Our core router is having stability problems right now. We’re working to resolve the issue. -Dane

Update: We’ve traced the trouble to a network attack on one of our dialup access servers which is apparently coming from someone at (or spoofing the address of) the University of Wisconsin. We isolated the source and filtered the traffic so that it no longer affects our network. -Dane

Thu May 28 17:11:32 PDT 1998 — Busies on 522-1001. For the last 45 minutes or so, Pacific Bell has been having difficulties with hunting between our 522-1001 and 522-1002 hunt groups, causing 522-1001 to return busy signals. We are working with Pacific Bell to get the problem solved as soon as possible; meanwhile, the 522-1002 and 522-1003 numbers are not affected. Update: Pacific Bell fixed their translations programming error around midnight last night. They apologized for the busy signals that some customers experienced due to their error. -Dane

Thu May 7 09:40:42 PDT 1998 — We will be rebooting the equipment that serves 522-1003 and 522-1389 this morning. The purpose is a firmware upgrade that containes several bug fixes for this equipment. We apologize for any inconvience. -Brian

Sat Apr 25 10:03:27 PDT 1998 — We had some authentication problems this morning which may have cause some of our customers to not be able to log in. In resolving this problem, we also had to reboot a few of our terminal servers. We apologize for any inconvience this may have caused. -Brian

Tue Apr 21 18:23:43 PDT 1998 — The access server which supports our v.90 pilot (nas22.sonic.net) had problems this afternoon, and we had to replace and reconfigure it’s route controler. 522-1389 was unavailable for a while this afternoon during this work. The failure occured while trying to upgrade the unit to a new engineering release of the operating system which is supposed to fix problems with the units rebooting. We’ve been experiencing this intermittently with nas21.sonic.net which serves 522-1003. If the OS had worked well on nas22, we would have upgraded nas21. -Brian (he did all the work)

Fri Apr 17 21:53:08 PDT 1998 — At approximately 3am tomorrow (Saturday) morning, we will be rebooting some servers to make changes to their operating systems. Included are www.sonic.net and mail.sonic.net — they will be unavailable for a a minute or two during the reboot. We apologize for any inconvenience. -Scott