Wed Aug 1 22:51:13 PDT 2007 — Upstream network issue. Connectivity via one of our upstream providers was impacted for a short time this evening as they were experiencing routing problems. Impact would have been inability to connect to certain websites. Our upstream provider corrected their issue approx. 30 minutes ago, and we continue to monitor the issue. -Jared

Sat Jul 28 18:40:50 PDT 2007 — At approximately 2:15pm a core router in San Jose failed. There was no customer impact, as our network shifted traffic through other links. After further testing, remote repairs could not be made on the failed equipment. Sonic.net NOC staff are currently en route to San Jose with a hot spare. — Matt and the NOC

Update Sat Jul 28 22:02:13 PDT 2007 — We have replaced the failed hardware in our San Jose POP, and all connectivity through that POP has been restored. Customer impact during this outage should have been minimal, as all traffic re-routed via our redundant ring to transit in other POPs. -Jared, Dusty, Zeke and Matt

Fri Jul 27 17:18:17 PDT 2007 — It’s Sonic.net’s 13th birthday!! We will be celebrating at our annual picnic on Saturday July 28, so technical support will be closed from 12 pm to 6 pm. NOC support will remain available all day, and tech support will return your messages after 6 pm when support re-opens. www.sonic.net/whatsnew/

Thu Jul 26 02:01:11 PDT 2007 — Maintenance completed. We have completed our DSL maintenance for the evening. Downtime was 2 minutes for customers in Sacramento, and approximately 10 minutes for customers in the Stockton area. We also performed our dialup move earlier today and have been monitoring the situation since. Aside from a brief problem with authentication, the dialup move went smoothly. -Jared and Dusty

Wed Jul 25 15:41:37 PDT 2007 — SpamAssassin Update. SpamAssassin has been updated to the latest stable release which came out today. While this upgrade was done primarily for bug fixes we took the opportunity to address the continued issue of PDF Spam. At this point we believe we are blocking most, if not all, of the current kinds of PDF spam seen and will continue to monitor and update our rules as needed. -Kelsey

Mon Jul 23 09:55:15 PDT 2007 — Dial Upgrades. This Wednesday, July 25th at 12:01 PM we will be moving the majority of our dial-up numbers to new hardware. The migration will cause any active calls to 522-1001 and any number ending with 3 to be dropped as we move the lines to the new gear. The new hardware provides many improvements over our prior gear, including v.92 support. -Jared, Dusty and Matt

Mon Jul 23 14:10:27 PDT 2007 — DSL Maintenance. On Thursday, July 26th at 12:01 AM we will be performing maintenance on the ATM backhaul circuits that serve the Stockton and Sacramento areas. Expected downtime is under 15 minutes for all customers in the affected areas. -Jared and Dusty

Mon Jul 16 12:07:52 PDT 2007 — DSL Aggregation Maintenance. On Tuesday, July 17th at 12:01 we will be performing backend system maintenance on the routers that terminate DSL for the Stockton/Modesto and Sacramento LATAs. Expected downtime is 15 minutes for DSL customers in those areas. -Nathan, Jared and Dusty

Update Tue Jul 17 01:47:16 PDT 2007 — We have completed our DSL maintenance for the evening. Actual downtime was approximately 5 minutes for affected customers. -Jared, Dusty and Nathan

Wed Jul 11 11:49:34 PDT 2007 — Upstream provider issue resolved. We have been monitoring a problem in one of our upstream providers that was causing latency to some sites in the AM hours. The upstream provider has taken actions that appear to have resolved the problem. We continue to monitor the situation. -Jared, Dusty and Nathan

Thu Jun 21 10:11:35 PDT 2007 — DSL Aggregation Equipment Maintenance. At 12:01am on Friday, June 22nd we will be performing emergency maintenance on a portion of our DSL aggregation infrastructure in San Francisco. Customers in Los Angeles as well as a large portion of our LATA 1 customers will be affected by this operation. Business-T customers served in those areas may also experience service interruption. While expected downtime is approximately 15 minutes, we’re reserving a one hour maintenance window in case of further trouble. -Nathan and Jared

Update Fri Jun 22 00:54:44 PDT 2007 — We’ve completed our work for the evening. Actual downtime was approximately 12 minutes for each affected customer. -Nathan and Jared