Salesforce: Performance Degradation: Email Studio
Affected components: Email Studio259 instances
Timeline of updates
- update
We’re investigating an issue impacting outbound email functionality on Stack 7. Initial findings indicate a significant decrease in database storage activity and elevated processor utilization on an associated database instance. We’re checking these observations to determine the underlying cause, with additional resources engaged to support and coordinate resolution efforts.
Further investigation has also revealed that the impact began earlier than initially identified. The Trust post has been updated to reflect the revised impact start time and provide a more accurate representation of when customers may have first experienced degradation. We apologize for any confusion caused by this correction.
We’re engaged in the investigation. We will provide the next update within 30 minutes, or sooner if significant new information becomes available.
- update
We identified that storage capacity supporting the databases for this instance is exhausted, and we are expanding storage to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
We completed the storage expansion for the first database cluster, and work is underway to expand storage for the second cluster. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- update
We added storage capacity to the affected database clusters, and email send volume are returning to expected levels. We are continuing to monitor the instances for recovery and stability. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
We are monitoring to confirm service remains stable. Some send jobs may have entered an error state during this time. We are confirming whether customers need to cancel and resend these jobs or whether we can resume them on our side, and we'll share guidance as soon as it's available. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
Some send jobs may have entered an error state and we are resuming these jobs on our side, and customers do not need to take action. We are monitoring to confirm service remains stable. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
We resolved the issue impacting outbound email sends. During this time, emails sends were delayed or failing to deliver, and some SMS sends that include links may also have experienced issues. We identified that the databases we use for link tracking ran out of storage capacity. We added storage capacity to the affected databases clusters, and email send volume has returned to expected levels. Some send jobs entered an error state during this time, and we will resume these jobs on our side. Customers don't need to take action. We apologize for the impact this incident may have had on our customers and their businesses. We'll thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Changes Rewindex caught on this incident
- Incident updated: Performance Degradation: Email Studio
- Incident updated: Performance Degradation: Email Studio
- Incident updated: Performance Degradation: Email Studio
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 these records existed by then and have 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-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
80d706b2f4b36dae…Version 2 captured
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
65e9870d13b17a04…Version 3 captured
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
17c057f35b810929…Version 4 captured
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
63bf80e57cfd2f52…
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-10-26 12:10 UTC, resolved after 3.1 h, 8 update(s); edited after publishing.
- Title
- Performance Degradation: Email Studio
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004532
Salesforce profileRecent Salesforce incidentsAll outages on October 26, 2026Salesforce in October 2026MarkdownJSON