Feature Degradation

The Salesforce Technology team is actively monitoring performance metrics following targeted restarts of the email system. After switching outbound email traffic to a healthy host, we observed performance improvements. The team will continue to monitor these metrics closely to ensure service levels stabilize and return to acceptable thresholds.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.

The Salesforce Technology team has ruled out network infrastructure as a trigger of this issue. Key email systems are currently undergoing targeted restarts, and we are closely monitoring these efforts to ensure complete stability.

The impacted instances have been updated to include: CAN54.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

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, BRA36, USA340, USA746, will receive communications related to this incident going forward.

We're actively investigating email service issues and reviewing network logs to identify the trigger of the issue. While we don’t have new updates to share at this time, our teams remain fully engaged and are working diligently to resolve the underlying problem.

The impacted instances have been updated to include: USA618, USA922, USA342, USA686, USA422.

We'll provide the next update within 60 minutes or sooner if new information becomes available

The Salesforce Technology team is continuing to monitor the impact closely after applying recent configuration changes to key service modules and jobs. While we haven't seen significant improvement yet, our teams remain fully engaged, investigating alternate solutions, and actively monitoring performance metrics. This issue remains a top priority for the Salesforce Technology team.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

In the pursuit of our recovery efforts, we have applied a configuration for some service modules and jobs. We are actively monitoring metrics to gauge any improvements while we continue to investigate alternate remediation paths.

This posting has been updated to include these additional impacted instances: USA650, NA226, USA384, USA430, USA676, USA548, NA249, USA478, USA1108, NA254, USA300, CAN50, USA418, USA326, NA225, USA356

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

We would like to clarify that this only impacts a subset of customers on the listed instances. Some customers on these instances may be experiencing delays with outgoing and incoming emails, such as Email-to-Case functionality. We have also noted that some customers may be experiencing login issues based on their configuration. We have also terminated stuck jobs and performed configuration changes to help with the recovery process.

This posting has been updated to reflect the additional instances: USA588, USA592, USA674, CAN56, USA742, USA600, USA546, NA237, USA726, USA736, USA720, SWE62, USA564, USA280, USA644, USA558, USA278, USA552, USA606, USA352, USA740

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

There are no new updates to share at this time. We continue to troubleshoot the issue that is slowing the recovery process.

We have updated the posting to reflect the additional instances: USA320, USA550, USA346, USA680, USA652, USA868, USA1, USA348, NA251, USA554, USA230, USA698, USA288, USA360, USA682, CAN46, USA648, USA410, USA920, USA374, USA744, USA330, USA332, USA426, BRA30, USA316, USA728, USA572, USA314, USA456, USA232, USA462, USA318, USA702, and USA576, 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.

We are awaiting the results of a mitigation that was performed on a test instance. While most mitigation actions are largely complete, the recovery is slower than anticipated. We are working to restore services as soon as possible.

We have updated the posting to reflect the additional instances: CAN36, NA236, NA225, USA226, USA230, USA274, USA276, USA282, USA296, USA312, USA346, USA372, USA414, USA426, USA464, USA438, USA466, USA544, USA584, USA610, USA716, USA718, USA730, and USA9008, 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.

We are actively clearing the backlog for both inbound and outbound emails, and the backlog has come down. We are working to restore services, and we apologize for how you and your business may have been affected.

We have updated the posting to reflect the additional instances: BRA48, CAN34, CAN44, USA234, USA238, USA294, USA302, USA304, USA354, USA376, USA428, USA632, USA408, USA442, USA454, USA538, USA566, USA570, USA616, USA634, USA646, USA684, USA692, USA694, USA696, USA714, USA852, USA854, USA856, USA864, and USA926, 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.

We are continuing to work on mitigating the impact and actively clearing the backlog for both inbound and outbound emails.

We have updated the posting to reflect the additional instances: USA34, USA292, USA336, USA424, USA436, USA440, USA468, USA472, USA496, USA574, USA580, USA604, USA624, USA678, USA732, USA810, and DEU36, experiencing impact, and customers in these instances will receive communications related to this incident going forward.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Upon investigation, we believe the issue is due to a spike in traffic, causing a backlog in inbound and outbound email. We have isolated the issue and are working on mitigating the impact.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances: NA242, USA476, and USA578, experiencing impact, and customers in these instances will receive communications related to this incident going forward.

Upon further investigation, we have determined that the start time of impact is different than initially understood. We have now revised the start time to 12:01 UTC and have updated this Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

Upon further investigation, we have determined that the start time of impact is different than initially understood. We have now revised the start time to 00:01 UTC and have updated this Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We are investigating a feature degradation that is impacting Email services for customers on NA239, NA240, NA241, NA243, NA244, NA246, NA248, NA250, NA252, and NA253. We are exploring multiple mitigation strategies.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.