Salesforce outage reports show an ongoing Core Service disruption on the company’s status page that began at 7:50 am UTC on Sep 16, affecting multiple AP and ARE region instances.
The incident page (ID 20004433) lists the status as “Ongoing” and names the impacted service as Core Service, with affected instances including AP52, AP53, AP54 and several ARE and AUS instances, and a timeline showing the disruption started at 3:50 am EDT on Sep 16.
Salesforce’s incident history on the status page says engineers found requests were stalling while waiting on an internal login service and that increased load on a core component limited its capacity to process requests.
Updates on the status page show the team validated a fix on a test instance and is rolling that fix out fleetwide region by region; the page warns customers may continue to see severe delays, intermittent errors, and inability to access some services while the rollout proceeds.
Salesforce’s status page is the primary source for the company’s real-time incident information and remains the authoritative place for updates during the outage; third-party monitors show elevated reports but direct customer impact details come from Salesforce’s incident updates.
Sources
- Salesforce Status — incident page ID 20004433 with timeline, impacted instances, cause analysis and remediation updates.
- Mirage News — reporting that the disruption began at 07:50 UTC on Sep 16 and noting the status page updates.
