Litmus incident

Planned Outage for Database Migration

Resolved after 5 days, on April 18, 2016.

completed Apr 23, 2016, 02:26 PM UTC

This outage was errantly scheduled for 9am.

Started
Apr 18, 2016, 02:20 PM UTC
Resolved
Apr 23, 2016, 02:26 PM UTC
Duration
5d
Detected by Pingoru
Apr 18, 2016, 02:20 PM UTC

Update timeline

  1. scheduled Apr 18, 2016, 02:20 PM UTC

    Litmus will be migrating one of the primary databases for site to a new environment this weekend. While steps have been taken to minimize the impact, some downtime will be required to ensure the consistency of the data and to ensure all applications are properly functioning. This change will also grant us the ability to further reduce or eliminate customer impact during similar significant upgrades in the future. During this window you can expect the Litmus application to be unavailable intermittently through either the main front end or the APIs. Secondary inputs that handle data for services like email analytics, spam, etc will continue to function as normal.

  2. scheduled Apr 23, 2016, 11:59 AM UTC

    Maintenance will begin as scheduled in 60 minutes.

  3. in progress Apr 23, 2016, 01:00 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  4. completed Apr 23, 2016, 02:26 PM UTC

    This outage was errantly scheduled for 9am.

Your product runs on more than Litmus

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →