# Salesforce: Performance Degradation: Email Studio

> Salesforce status incident “Performance Degradation: Email Studio” on 2026-10-26: impact minor (vendor’s label), 3.1 h, 8 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/salesforce/incidents/20004532
Last updated: 2026-10-26T16:33:00Z

- Impact (vendor’s label): minor
- Status: resolved · edited after publishing
- Started: 2026-10-26 12:10 UTC · Resolved: 2026-10-26 15:18 UTC · Duration: 3.1 h
- Updates: 8 · Affected components: Email Studio, 259 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004532](https://status.salesforce.com/incidents/20004532)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-10-26 15:03 UTC: 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** 2026-10-26 15:10 UTC: 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** 2026-10-26 15:18 UTC: 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** 2026-10-26 15:23 UTC: 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** 2026-10-26 15:29 UTC: 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** 2026-10-26 15:46 UTC: 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** 2026-10-26 15:55 UTC: 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** 2026-10-26 16:03 UTC: 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.

## Rewindex changes for this incident

- 2026-10-26 15:33 UTC: [Incident updated: Performance Degradation: Email Studio](https://rewindex.com/change/r399147b08b445e.md)
- 2026-10-26 16:03 UTC: [Incident updated: Performance Degradation: Email Studio](https://rewindex.com/change/r3b818964577436.md)
- 2026-10-26 16:33 UTC: [Incident updated: Performance Degradation: Email Studio](https://rewindex.com/change/ra607478717ed9d.md)

## 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.

- Canonical URL: https://rewindex.com/company/salesforce/incidents/20004532
- Citation: Salesforce, “Performance Degradation: Email Studio” (2026-10-26 12:10 UTC). Archived by Rewindex: https://rewindex.com/company/salesforce/incidents/20004532 (CC BY 4.0).
- Markdown link: `[Salesforce: Performance Degradation: Email Studio (2026-10-26)](https://rewindex.com/company/salesforce/incidents/20004532)`


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004532 · Markdown: https://rewindex.com/company/salesforce/incidents/20004532.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004532 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T14:15:26.809Z