Author: dexter.keen@sonic.com

Between March 5 at 11:40 AM and March 6 at 10:00 AM PST, some DNS queries to ns2.sonic.net (50.0.2.2) were intermittently failing due to stale process state on one of our DNS cluster nodes following a scheduled network migration. The issue has been resolved and service is operating normally. We are updating our post-migration verification procedures to prevent recurrence.

Update: Maintenance complete.

Tonight beginning at 10 PM PST we will be applying updates to our VPN cluster which will require us to reboot each node.  The maintenance should only last around 15 – 30 minutes.  Thanks for choosing Sonic!

On Friday, October 24th at 11am PST we will be upgrading our VPN cluster to modify the minumum supported TLS encryption version from 1.1 to 1.2.  Our analysis shows that we do not have any active users connecting with TLS 1.1, however we still wanted to provide this notice for your information. Thank you for your understanding, and thanks for choosing Sonic!

– System Operations team

Update: This maintenance is complete.

This maintenance has been rescheduled for Thursday, June 6th at 10PM PST.

On Thursday May 29th, beginning at 10pm PST we will be upgrading components of our customer VPN infrastructure.  In order to facilitate these upgrades there will be a small window of downtime for the service.  It is estimated that the window for this operation should span no longer that 30 minutes, and during that time the service availability may fluctuate.  Thank you for your understanding and support – Sonic System Operations

Update: 10:48 PM PST Maintenance is complete.

Tonight we will be applying updates to systems including forums.sonic.net, as well as webmail and our VPN servers. These systems will have limited availability during the window, beginning at 10pm PST, and hopefully completed within 2 hours. Thanks – Sonic System Operations

Tonight at 10pm we will be upgrading the operating system on the Sonic customer FTP server ftp.sonic.net. We expect the service downtime to be brief and no longer than 1 hour in total.

Update: This maintenance has been completed successfully.