Salesforce: Feature Perf Degradation: Email Studio
Affected components: Email Studio44 instances
Timeline of updates
- update
Between 11:02 and 11:34 UTC on January 22, 2026, a fix implemented for a separate issue impacted triggered sends for a subset of customers across Stack 1. During this time, triggered sends stopped and customers may have received alert notifications from Alert Manager and proactive monitoring indicating their sends weren't functioning.
We automatically restarted all impacted triggered sends and customers do not need to take any action. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a1b75a50c0f162d7…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-01-22 11:02 UTC, resolved after 32 min, 1 update(s).
- Title
- Feature Perf Degradation: Email Studio
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003606
Salesforce profileRecent Salesforce incidentsAll outages on January 22, 2026Salesforce in January 2026MarkdownJSON