Outage in Salesforce
Marketing Cloud Engagement Feature Disruption
Resolved Minor
May 15, 2025 - Started about 18 hours ago
- Lasted about 5 hours
Need to monitor Salesforce outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Salesforce, and never miss an outage again.
Start Free Trial
Outage Details
The Salesforce Technology team identified a feature disruption affecting customers on this instance and is working to resolve it. During a Marketing Cloud Engagement feature disruption, end users are unable to access certain aspects of the affected service. We’re investigating the issue and will provide updates as soon as possible. See Impacted Services and Additional Information for further details.
Components affected
Salesforce DB401000 Salesforce DB401001 Salesforce DB401002 Salesforce DB401003 Salesforce DB401004 Salesforce DB401005 Salesforce DB401006 Salesforce DB401008 Salesforce DB401009 Salesforce DB401011 Salesforce DB401012 Salesforce DB401013 Salesforce DB401014 Salesforce DB401016 Salesforce DB401017 Salesforce DB402000 Salesforce DB402001 Salesforce DB402002 Salesforce DB402003 Salesforce DB402004 Salesforce DB402005 Salesforce DB402006 Salesforce DB402008 Salesforce DB402009 Salesforce DB402010 Salesforce DB402011 Salesforce DB402012 Salesforce DB402013 Salesforce DB402014 Salesforce DB402015 Salesforce DB402016 Salesforce DB402017 Salesforce DB402018 Salesforce DB402019 Salesforce DB402020 Salesforce DB402021 Salesforce DB402022 Salesforce DB402023 Salesforce DB402024 Salesforce DB402025 Salesforce DB402026 Salesforce DB402027 Salesforce DB402028 Salesforce DB402029 Salesforce DB402030 Salesforce DB402031 Salesforce DB402032 Salesforce DB403000 Salesforce DB403001 Salesforce DB403002 Salesforce DB403003 Salesforce DB403004 Salesforce DB403005 Salesforce DB403006 Salesforce DB403008 Salesforce DB403009 Salesforce DB403010 Salesforce DB403011 Salesforce DB403012 Salesforce AUS102 Salesforce AUS14S Salesforce AUS16S Salesforce AUS18S Salesforce AUS20S Salesforce AUS22S Salesforce AUS24S Salesforce AUS26S Salesforce AUS28S Salesforce AUS2S Salesforce AUS36S Salesforce AUS38S Salesforce AUS4S Salesforce AUS58 Salesforce AUS60 Salesforce AUS62 Salesforce AUS64 Salesforce AUS66 Salesforce AUS68 Salesforce AUS6S Salesforce AUS70 Salesforce AUS72 Salesforce AUS74 Salesforce AUS76 Salesforce AUS78 Salesforce AUS80S Salesforce AUS82 Salesforce AUS84 Salesforce AUS86 Salesforce AUS88 Salesforce AUS90 Salesforce AUS92 Salesforce AUS94 Salesforce CAN20S Salesforce CAN26 Salesforce CAN28 Salesforce CAN2S Salesforce CAN34 Salesforce CAN36 Salesforce CAN38 Salesforce CAN40 Salesforce CAN42 Salesforce CAN44 Salesforce CAN46 Salesforce CAN48 Salesforce CAN4S Salesforce CAN50 Salesforce CAN52 Salesforce CAN54 Salesforce CAN56 Salesforce CAN6S Salesforce CAN70S Salesforce CAN80 Salesforce CAN86S Salesforce CAN8S Salesforce IND100 Salesforce IND102 Salesforce IND104 Salesforce IND108 Salesforce IND10S Salesforce IND110 Salesforce IND112 Salesforce IND114 Salesforce IND116 Salesforce IND118 Salesforce IND120 Salesforce IND122 Salesforce IND124 Salesforce IND126 Salesforce IND128 Salesforce IND12S Salesforce IND132 Salesforce IND134 Salesforce IND136 Salesforce IND138 Salesforce IND14S Salesforce IND16S Salesforce IND18S Salesforce IND20S Salesforce IND22S Salesforce IND24S Salesforce IND26S Salesforce IND28S Salesforce IND2S Salesforce IND3S Salesforce IND4S Salesforce IND54S Salesforce IND58 Salesforce IND60 Salesforce IND62 Salesforce IND64 Salesforce IND66 Salesforce IND68 Salesforce IND6S Salesforce IND70 Salesforce IND72 Salesforce IND74 Salesforce IND76 Salesforce IND78 Salesforce IND80 Salesforce IND82 Salesforce IND84 Salesforce IND86 Salesforce IND88 Salesforce IND8S Salesforce IND90 Salesforce IND92 Salesforce IND94 Salesforce IND96 Salesforce IND98 Salesforce JPN10S Salesforce JPN12S Salesforce JPN132 Salesforce JPN134 Salesforce JPN136 Salesforce JPN138 Salesforce JPN140 Salesforce JPN142 Salesforce JPN144 Salesforce JPN146 Salesforce JPN18S Salesforce JPN20S Salesforce JPN22S Salesforce JPN24S Salesforce JPN28S Salesforce JPN2S Salesforce JPN4S Salesforce JPN6S Salesforce JPN8SLatest Updates ( sorted recent to last )
UPDATE
about 13 hours ago - at 05/15/2025 12:49PM
Following successful testing, the change is being rolled out in a staggered manner across impacted databases. Customers may see signs of improvement as the deployment progresses.
We’ll update in 60 minutes or sooner if additional information becomes available.
UPDATE
about 14 hours ago - at 05/15/2025 12:00PM
The configuration change to resolve the identified mismatch between environments is still underway. The change is being reviewed and approved before being deployed. Once deployed, the team will validate whether it provides positive results.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
UPDATE
about 14 hours ago - at 05/15/2025 11:21AM
After further investigation, the issue could not be recreated in the test environment, and the continued deployment of the rollback would not be effective in resolving the issue. At this time the team is pursuing a fix forward by performing a manual configuration change to resolve the mismatch observed between the test and production environments. Additional teams have been engaged to assist in performing this mitigation step. Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
UPDATE
about 16 hours ago - at 05/15/2025 09:35AM
The rollback is still in progress. However, further investigations have revealed that it might not resolve the underlying issue, as the changes were implemented at the Kubernetes level. As a contingency plan, we are exploring other paths to resolution simultaneously with the rollback.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
UPDATE
about 17 hours ago - at 05/15/2025 08:26AM
We have initiated a rollback of the recent release in a Test environment, which will take approximately 90 minutes to complete. We will continue to monitor the results closely.
We’ll provide an update in 90 minutes or sooner if additional information becomes available.
UPDATE
about 17 hours ago - at 05/15/2025 08:17AM
At 23:00 UTC, on May 14, 2025, the Salesforce Technology team was alerted to a feature disruption with the Content Builder feature within Marketing Cloud Engagement across multiple Hyperforce instances. Initial investigations have determined that a recent change could be the potential trigger of the issue. Additionally, the investigations have revealed that the start time of impact is different than initially understood. We have now revised the start time of the incident. We are preparing a rollback of the recent change in a Test environment. Customers attempting to create mobile-related content, such as SMS, push, or in-app messages, are encountering 404 errors.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Latest Salesforce outages
Service Disruption - about 7 hours ago
Performance Degradation - about 14 hours ago
Data Cloud Feature Degradation - about 20 hours ago
Performance Degradation - about 22 hours ago
Feature Disruption - 1 day ago
All Your Service Status Pages in One Dashboard
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 4200 services available
Integrations with
