We continue to work on restoring the Marketing Cloud Engagement database. A replacement of a failed component on the storage array has been planned, and is expected to take a few hours. The replacemen

Update timeline

1. identified Sep 18, 2026, 01:06 PM UTC

   Disruption Started: serviceDisruption

2. monitoring Sep 18, 2026, 01:24 PM UTC

   We're investigating an issue impacting a database supporting Marketing Cloud Engagement, and customers on the impacted database are currently unable to connect. Our investigation points to a potential file lock as the trigger. We've engaged additional support and are preparing a secondary environment in case it is needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 18, 2026, 01:49 PM UTC

   We're continuing to investigate a disruption impacting a database supporting Marketing Cloud Engagement, and affected customers remain unable to connect. We've identified that a storage-level lock is likely preventing the database from completing recovery, and our engineering teams are working to resolve it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 18, 2026, 02:15 PM UTC

   We've ruled out a storage-level file lock as a factor in the ongoing recovery issue impacting Marketing Cloud Engagement. Affected customers remain unable to connect to services on the impacted database. We've started taking the database offline and bringing it back online in an effort to complete recovery. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 18, 2026, 02:45 PM UTC

   We've performed an in-place restart of the impacted Marketing Cloud Engagement database which has moved into a recovery state. Affected customers remain unable to connect to services while recovery completes. We're monitoring progress closely. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Sep 18, 2026, 03:16 PM UTC

   Affected customers remain unable to connect to the Marketing Cloud Engagement database affected by this incident. We're now evaluating whether to continue recovery efforts on this database or move forward to our secondary database, which is fully prepared. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Sep 18, 2026, 03:55 PM UTC

   We continue to work on restoring the Marketing Cloud Engagement database. A replacement of a failed component on the storage array has been planned, and is expected to take a few hours. The replacement will run parallel to our recovery work without affecting it. We'll provide an update in 30 minutes or sooner if additional information becomes available.