Sun May 11 22:04:14 PDT 2003 — Dial-up outage on 0174 numbers. An equipment failure caused dropped connections and busy signals on our xxx-xxx-0174 numbers in southern and inland California. The equipment was rebooted and is now taking calls.
Southern California numbers ending with 9606 are on a separate system and were not effected. Note: -Russ and Matt
Thu May 8 09:36:27 PDT 2003 — Broadlink trouble last night. Last night, between 8:46pm and 9:15pm, Broadlink had a sector down on one of their towers. 62 customers were affected during the outage. -Scott, and Tim, Jason from Broadlink
Wed May 7 15:56:49 PDT 2003 — Redback reboot. Our Redback SMS that serves San Francisco area SBC DSL customers needed to be rebooted just now. It has come back up and customers are being added to the network now. -Kelsey and John
Tue May 6 11:52:31 PDT 2003 — An equipment failure at our San Francisco POP has caused some capacity problems for dial-up numbers ending in 9811. We’ve got engineers on site working to replace the bad equipment now, and we’re hoping to be back to normal capacity by 1:00pm or so. We have alternate numbers for all coverage areas, see: www.sonic.net/cgi-bin/pops.pl for alternate dialups. – Eli, OPS, Support
Tue May 6 16:04:34 PDT 2003 — Tomorrow morning we will be migrating ftp.sonic.net to a pair of new load balanced servers. The new servers support FTP-TLS, which enables encryption of authentication, and eliminates the need to pass passwords in clear-text over the network. There is limited support for FTP-TLS; most common FTP clients support it, although in some cases only the registered or ‘pro’ versions. Sonic offers only one remaining service that requires clear-text passwords; SMTPAUTH, which will be resolved when we enable SMTP-TLS in the near future. We will also be enabling FTP-TLS on ssl.sonic.net. For more information on FTP-TLS please see makeashorterlink.com/?N3D512874 -Kelsey
Tue May 6 14:21:45 PDT 2003 — Engineers continue to work on the equipment problem for the piece of gear in the 9811 hunt group. They have swapped out the “brains” of the unit, and are currently configuring it. The problem should be alleviated soon. -Scott, Support, and OPS (including Russ, Matt K., and John H. in SF)
UPDATE: Repairs have been completed. The 9811 hunt group has been restored to service and is taking connections again. -OPS, Support
Tue May 6 00:50:50 PDT 2003 — Night Ops Completed. Our customer MySQL server’s upgrade is complete. Please note that in this process the server’s IP address changed and that if you are referring to it by IP you’ll need to update to use the proper hostname, ‘mysql.sonic.net.’ The router maintenance went smoothly, no service interruption was generated. -Kelsey and Nathan
Mon May 5 15:27:39 PDT 2003 — Tonight, shortly after Midnight we will be making a few routine configuration updates to our main customer router. We do not anticipate any service interruption. -Nathan and Kelsey
Mon May 5 14:26:14 PDT 2003 — Customer MySQL server upgrade: We are going to replace our existing customer MySQL server with a new server tonight. The new server will be running a new OS and the standard MySQL version 4 distribution. This new MySQL server offers a number of new features over the old v3 server and should offer marginally increased performance. We do not anticipate that any MySQL customers will encounter any issues after this upgrade but encourage everyone to check their applications for problems tomorrow morning. -Kelsey
Fri May 2 11:21:58 PDT 2003 — Link errors to San Jose resolved. Our vendor discovered the congested link that was causing problems and our performance problems have been resolved. We continue to monitor this link. -Scott, Nathan, Matt and John.