The engineering teams have identified the root cause of the issue and are currently developing a fix.
Until the fix is fully deployed, customers may receive proactive monitoring and Alert Manager notifications of triggered sends failing. To resume any high-priority, interrupted triggered send jobs, customers can manually republish them.
We'll share another update as soon as further information becomes available.
The tokenization rollout is now complete across all Stacks with the partial fix being applied to all databases on Stack 51 as of 02:36 UTC.
Our teams are still actively working to troubleshoot the cause of the email delivery issues.
We'll share another update as soon as further information becomes available.
As of 01:37 UTC, the partial fix has been applied to all DBs on Stack 6.
As of 01:55 UTC, the partial fix has been applied to all DBs on Stack 12.
As of 02:15 UTC, the partial fix has been applied to all DBs on Stack 13.
We'll begin rolling out the partial fix to Stack 51 shortly. During the rollout, triggered sends may stop, and customers may receive alerts from Alert Manager and proactive monitoring that their sends aren't working. Customers can republish any interrupted jobs that need prioritization after the partial fix has been applied.
We'll provide another update as soon as we have more information to share.
While the fix we are rolling out to the DBs referenced in the following Trust posts is allowing more email delivery successes to some mailbox providers, further monitoring and analysis indicates that error rates remain elevated.
https://status.salesforce.com/incidents/20003607
https://status.salesforce.com/incidents/20003608
https://status.salesforce.com/incidents/20003609
https://status.salesforce.com/incidents/20003610
https://status.salesforce.com/incidents/20003611
The instances in these posts have been reincorporated into this incident. Updates for all impacted instances will be posted here going forward. As this partial fix does provide some relief, we will continue to roll this out to the remaining impacted DBs.
As of 20:06 UTC, the partial fix has been applied to all DBs on Stack 11.
As of 20:38 UTC, the partial fix has been applied to all DBs on Stack 50.
Our teams are continuing to troubleshoot and isolate the trigger of the email delivery issues. We'll provide another update as soon as we have more information to share.
We will begin rolling out the partial fix to Stack 4 shortly. During the rollout, triggered sends may stop, and customers may receive alerts from Alert Manager and proactive monitoring that their sends are not working. These alerts can be ignored.
We'll provide another update as soon as we have more information to share.
As of 21:34 UTC, the partial fix has been applied to all DBs on Stack 4.
Our teams are continuing to troubleshoot and isolate the trigger of the email delivery issues. We'll provide another update as soon as we have more information to share.
We will begin rolling out the fix to Stack 11 shortly. During the rollout, triggered sends may stop, and customers may receive alerts from Alert Manager and proactive monitoring that their sends are not working. These alerts can be ignored.
We'll provide another update as soon as we have more information to share.
As of 19:21 UTC, a fix has been applied to all DBs on Stack 7. Email delivery to certain mailbox provider domains should now be functioning as expected. All Stack 7 DBs will be removed from this posting going forward. Please see the following dedicated posting: https://status.salesforce.com/incidents/20003611.
We’re continuing to apply the fix to the remaining impacted DBs in a staggered manner. During the rollout, triggered sends may stop, and customers may receive alerts from Alert Manager and proactive monitoring that their sends are not working. These alerts can be ignored. We apologize for the continued impact and will notify you as we make progress.
As of 19:21 UTC, a fix has been applied to all DBs on Stack 5. Email delivery to certain mailbox provider domains should now be functioning as expected. All Stack 5 DBs will be removed from this posting going forward. Please see the following dedicated posting: https://status.salesforce.com/incidents/20003610.
We’re continuing to apply the fix to the remaining impacted DBs in a staggered manner. We apologize for the continued impact and will notify you as we make progress.
As of 18:42 UTC, a fix has been applied to all DBs on Stack 8. Email delivery to certain mailbox provider domains should now be functioning as expected. All Stack 8 DBs will be removed from this posting going forward. Please see the following dedicated posting: https://status.salesforce.com/incidents/20003609.
We’re continuing to apply the fix to the remaining impacted DBs in a staggered manner. We apologize for the continued impact and will notify you as we make progress.
As of 17:38 UTC, a fix has been applied to all DBs on Stack 10. Email delivery to certain mailbox provider domains should now be functioning as expected. All Stack 10 DBs will be removed from this posting going forward. Please see the following dedicated posting: https://status.salesforce.com/incidents/20003608.
We’re continuing to apply the fix to the remaining impacted DBs in a staggered manner. We apologize for the continued impact and will notify you as we make progress.
We will begin rolling out the fix to Stack 10 shortly. During the rollout, triggered sends may stop, and customers may receive alerts from Alert Manager and proactive monitoring that their sends are not working. These alerts can be ignored.
We'll provide another update as soon as we have more information to share.
As of 11:34 UTC, a fix has been applied to all DBs on Stack 1. Email delivery to certain mailbox provider domains should now be functioning as expected. All Stack 1 DBs will be removed from this posting going forward. Please see the following dedicated posting: https://status.salesforce.com/incidents/20003607.
We’re continuing to apply the fix to the remaining impacted DBs in a staggered manner. We apologize for the continued impact and will notify you as we make progress.
We continue to work on preparing a fix, which will resolve the issue. Once prepared, the fix will be tested and once validated will be rolled out to impacted Stacks in a staggered manner.
We'll provide an update as soon as we have more information to share.
We have determined that a recent code change caused a configuration conflict with our third-party provider. We're preparing a fix, which will resolve the issue.
We'll provide an update in 120 minutes or sooner as additional information becomes available.
At 18:04 UTC on January 20, 2026, we began investigating a feature degradation affecting email delivery for a subset of customers.
Customers sending emails to certain mailbox provider domains may experience slightly higher bounce rates. All other services remain operating normally. We have identified an email configuration issue with our third-party provider and are actively working to resolve it.
We will provide an update in 60 minutes or sooner as additional information becomes available
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 · 5420 services available
Integrations with