Live  /  Salesforce  /  Incident

Salesforce: Degradation: EmailStudio (259 instances)

Salesforce · salesforce.comMinor incidentResolved2026-10-26 15:46 UTC
Public — what happened

Summary

Salesforce said a minor problem affected outbound email sending in Email Studio on its Stack 7 instance, beginning around 14:50 UTC on 2026-10-26, though it later said the impact may have started earlier than first stated. The company said it found that storage space for the databases behind this instance had run out, and it added capacity to the affected database clusters. By 15:29 UTC it reported email sending volumes returning to expected levels, and at 15:46 UTC it was still watching to confirm stability. Salesforce said some send jobs may have ended in an error state and it was working out whether customers must cancel and resend them or whether it can resume them itself; the incident was not marked resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Salesforce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Salesforce: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Salesforce report →

More from Salesforce

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Salesforce status & history page.

Related: Salesforce status & history. SquidGrid is not affiliated with Salesforce.