Flying Sphinx incident

Priapus Primary is restarting

Notice Resolved View vendor source →

Flying Sphinx experienced a notice incident on July 6, 2017, lasting 35m. The incident has been resolved; the full update timeline is below.

Started
Jul 06, 2017, 04:20 AM UTC
Resolved
Jul 06, 2017, 04:55 AM UTC
Duration
35m
Detected by Pingoru
Jul 06, 2017, 04:20 AM UTC

Update timeline

  1. identified Jul 06, 2017, 04:20 AM UTC

    The primary priapus server has just unexpectedly restarted. The affected customers have been switched over to the secondary (failover) server. I'll work on getting the old primary rebooted as the new secondary.

  2. monitoring Jul 06, 2017, 04:51 AM UTC

    New secondary server is up for priapus.

  3. resolved Jul 06, 2017, 04:55 AM UTC

    Everything's back to normal, this incident is now resolved.