Syncrofy incident

Emergency Security Maintenance to Resolve Glibc Vulnerability

Critical Resolved View vendor source →

Syncrofy experienced a critical incident on February 18, 2016, lasting 3h 7m. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2016, 08:38 PM UTC
Resolved
Feb 18, 2016, 11:45 PM UTC
Duration
3h 7m
Detected by Pingoru
Feb 18, 2016, 08:38 PM UTC

Update timeline

  1. scheduled Feb 18, 2016, 08:38 PM UTC

    The Syncrofy Cloud Servers will be undergoing emergency maintenance tonight to address a potential vulnerability recently discovered in the Linux operating system. A patch was just made available for this vulnerability, and the Syncrofy team has successfully tested it in our QA environment. We will be applying this patch to our production servers tonight, shortly after 6:00 PM EST, which will result in downtime of a few minutes. No customer action is necessary. Local agents will continue to process data and once the web application is back online, all data processed during that downtime will be available. For more information on this particular vulnerability please see http://www.infoworld.com/article/3033862/security/patch-now-unix-bug-puts-linux-android-and-ios-systems-at-risk.html If you have any questions, please let us know.

  2. scheduled Feb 18, 2016, 09:59 PM UTC

    Maintenance will begin as scheduled in 60 minutes.

  3. in progress Feb 18, 2016, 10:59 PM UTC

    Our security maintenance has begun.

  4. monitoring Feb 18, 2016, 11:20 PM UTC

    Services have been patched and restored, we are running health checks to verify the changes.

  5. completed Feb 18, 2016, 11:45 PM UTC

    Our security maintenance is complete, and we have validated that the system is functioning normally.