Salesforce outage, October 2026: Service disruption on USA1230
Salesforce is reporting an incident: Service disruption on USA1230. It is still open.
!Degraded
From Salesforce's official status page, in their words.
What happened
- Started
- Status
- update
- Duration
- 3 days so far
- Impact
- major
- Affected
- USA1230
Why it happened
Salesforce has not given a cause yet. We never guess one.
Timeline
Newest first. From Salesforce's official status page, in their words.
- update
We’ve confirmed that some traffic is being routed through a newly added network path before its addresses are authorized by dependent services. Requests using this path may time out or fail intermittently. Teams are working with our third-party service provider and internal access teams to restore administrative console access needed for mitigation. Once access is available, Engineering plans to remove the affected route in a test environment, validate that connectivity recovers, and then apply the change to production. Alternative mitigations include potentially disabling the new proxy cluster or completing the required network permissions. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- update
Engineering identified a network-routing issue involving a recently added proxy path. Traffic sent through this path is intermittently failing because the required network permissions were not in place before traffic was enabled. Teams are preparing to remove the affected path from service so traffic uses the existing healthy route. Access to the cloud management console is currently unavailable, and Salesforce is engaging the cloud provider to restore access and proceed with the mitigation. Planned migration activity involving the affected instance remains paused as a precaution. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- update
Engineering has identified a likely network configuration issue involving a recently added traffic-routing path. Some requests using this path are timing out when connecting to supporting services. Teams are evaluating two mitigation options: removing the new routing path or completing the required network permissions so traffic can flow successfully. As a precaution, planned migration activity involving the affected instance has been paused while mitigation is in progress. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- update
We're investigating an issue affecting connectivity between some Salesforce environments and Long-Term File Storage. Customers may experience delays or intermittent failures when accessing files, and org migrations are being impacted. Our teams are actively investigating and working to restore normal connectivity. We'll provide an update in 30 minutes or sooner if additional information becomes available.
What this means for a business
- Pause scheduled campaigns if you can; otherwise they queue and send when it is back.
- Reply to urgent customers from your normal mailbox.
- Form leads and chats are usually kept and delivered late, not lost.
The full guide: what to do when a service you rely on is down
Other Salesforce incidents
- Marketing applications for starter pro suite foundations feature dis on CAN40, CAN42, GBR54, GBR70, open, update
- Feature perf degradation on JPN170, open, implementingsolutionworkingonfix
- Performance degradation on CHE16, CHE30, open, update
- Feature service disruption on BRA14, BRA24, BRA36, BRA48, open, investigatingcauseofissue
- Feature perf degradation on DEU54, DEU96, GBR46, GBR64, open, update
Hear about the next Salesforce incident as it starts
Free email alerts when the official status changes, with what to do while it is down.