Category: Uncategorized

Beginning at midnight on Thursday, September 29th we will be performing cable repairs in Sebastopol. We expect the maintenance to continue through the night and anticipate completion by early morning. A small subset of Sonic Fiber customers in Sebastopol may experience intermittent or loss of service during the maintenance window.

Update(9/30 8:22am): We experienced complications during repairs and are still working as quickly as possible to restore service to affected customers. Estimated time to repair completion is one hour.

Update(9:26am): Backbone splicing is complete and we are now working to restore individual customer strands. Customers should begin to come back online over the next 30 minutes, at which point we are expecting all service to be restored.

Update(5:41pm): The outside plant team has isolated another issue and expects it to be resolved within 2 hours.

Update(6:59pm): All services restored.

– Brian & Andrew

UPDATE: Maintenance complete.

Starting tonight at 11:59pm, SOC will be running system updates. The following services may experience brief interruptions:

• Customer web hosting
• IMAP/POP3/SMTP
• Open VPN
• IPv6 Tunnels

An update will be posted when the maintenance is complete.

SOC

We will be doing non-intrusive maintenance on our voice switch at 12:00 am on September 22, 2016.

NOC

Update: 2:00 am 9/22/2016 Maintenance is complete.

We are currently seeing routing issues with a major transit provider in the LA area, that may have caused some connectivity issues for users trying to reach destinations in the area. We are working with the provider on a resolution while we route around the issue.

• Noc

Update (12:39AM): Maintenance complete.

Beginning tonight, at midnight, we will be performing maintenance on Sonic Switched Ethernet circuits. The maintenance window for this procedure is 3 hours, but downtime is not expected to be more than 30 minutes.

• Network Engineering

Wednesday, September 14th at 6:00am we will be performing intrusive maintenance on our Fiber network in the Sunset district. This maintenance may affect connectivity for Fiber services on 26th, 28th, and 29th avenues. Downtime is expected to be less than an hour.

– Dan and Brian

Update: 6:15am – Maintenance is complete and service is restored.

Update 2:34am: Service has been restored.

We are currently experiencing an outage affecting legacy DSL users in the Chico area. The issue is still being investigated and we will update this message once we have an ETR.

• Michael

Tonight, August 29, starting at midnight, we will be performing software updates on core network equipment. Traffic is expected to route around the affected equipment, but customers may experience a brief period of routing instability as traffic shifts.

Update(1:00am): A portion of this maintenance is now complete, and the remainder is rescheduled for tomorrow night (August 30)

Update(8/31 1:57am): Maintenance complete.

-Tomoc

Tonight, August 29, starting at midnight, we will be performing a maintenance reload of equipment serving some legacy DSL and Business-T customers in the greater bay area and Los Angeles. Expected downtime is 15 minutes.

Update(12:15am): Maintenance complete

-Tomoc

A small group of people in the San Francisco area may be experiencing a loss of internet connectivity after last nights maintenance.  We are working with our dispatch and tech support teams to get the affected customers fixed as soon as we can. The cause of the outage is unknown at this time as we are also working with our vendor for insight into the issue.

Brandon

Update 10:48am: The outage is affecting a greater number of customers.  We are working aggressively with our vendor.  We will update when more information is available.

Update 2:46pm We have repaired the majority of the fiber customers impacted by the outage.  Additional affected customers have been identified and we will be reaching out to schedule replacent of the failed ONTs onsite.  The cause of outage was narrowed down to the combination of a previously unidentified software defect in the ONT, and an unlikely load issue upstream (that has been remedied).