ProcedureFlow incident

Infrastructure upgrades

Notice Resolved View vendor source →

ProcedureFlow experienced a notice incident on April 13, 2016, lasting 3d 14h. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2016, 01:28 PM UTC
Resolved
Apr 17, 2016, 04:24 AM UTC
Duration
3d 14h
Detected by Pingoru
Apr 13, 2016, 01:28 PM UTC

Update timeline

  1. scheduled Apr 13, 2016, 01:28 PM UTC

    We are performing maintenance to improve performance and reliability of ProcedureFlow. During this maintenance, ProcedureFlow will be unavailable. We expect the maintenance to last for 15 minutes. Here are the technical details: - Migrating to new Redis instances to improve performance and reliability based on recommendations from Amazon. - Upgrading our primary database to a new version.

  2. in progress Apr 17, 2016, 04:00 AM UTC

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

  3. in progress Apr 17, 2016, 04:16 AM UTC

    The migration to a new Redis instance is complete. However, our primary database is taking longer than expected. We're continuing to monitor while the upgrade completes. We apologize for the extended delay and inconvenience.

  4. completed Apr 17, 2016, 04:24 AM UTC

    Both the Redis instance migration as well as the the primary database upgrade have completed. Thank you for your patience.