Empist incident

Hosted Exchange Database Issue

Notice Resolved View vendor source →

Empist experienced a notice incident on September 8, 2015, lasting 20d. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2015, 04:33 PM UTC
Resolved
Sep 28, 2015, 05:32 PM UTC
Duration
20d
Detected by Pingoru
Sep 08, 2015, 04:33 PM UTC

Update timeline

  1. identified Sep 08, 2015, 04:33 PM UTC

    We are experiencing an issue with 2 of the databases in our Hosted Exchange cluster. Our team is working on the issue. No ETA is currently available but updates will be posted on this page. All email will be delivered when the database access has been restored.

  2. identified Sep 08, 2015, 05:49 PM UTC

    Email connectivity has been restored for mailboxes on the problem databases. Our team is in the process of syncing mailbox contents prior to the failure. If prompted by outlook, select use "Temporary Mailbox" until we all of the email synced.

  3. identified Sep 08, 2015, 07:18 PM UTC

    The sync repair is running as expected. We have confirmed connectivity for all users on the 2 databases. Another update will be added as we progress through this process.

  4. identified Sep 09, 2015, 01:47 AM UTC

    Our team is continuing to monitor the issue and working towards final resolution. Mailbox access is still available while older emails begin to populate into your mailbox.

  5. identified Sep 09, 2015, 05:25 AM UTC

    One of the databases has been synced and online with all mailbox items. The team has been working on the other database in parallel. Another update will be added once it is also online.

  6. identified Sep 09, 2015, 12:10 PM UTC

    Expected resolution for the remaining database is 8:15AM CT. We will provide another update as soon as one is available.

  7. monitoring Sep 09, 2015, 01:19 PM UTC

    Database is online and full mailbox details are available. Our team will continue to monitor for any issues. If you experience any problems, please close and re-open outlook. If the problem persists, please contact support.

  8. resolved Sep 28, 2015, 05:32 PM UTC

    This incident has been resolved.