- Level
- confirmed
- Worst impact
- Degraded
- Components
- coreService
- Regions
- usa710s, usa712s, usa714, usa716, usa718, usa720, usa722, usa724, usa726, usa728, usa730, usa732, usa734, usa736, usa738, usa740, usa742, usa744, usa746, usa748, usa750s, usa752s, usa754s, usa756s, usa758s, usa760s, usa762s, usa764s, usa766s, usa768s, usa770s, usa772s, usa774s, usa776, usa778, usa780, usa786s, usa788, usa790, usa792s, usa804s, usa810, usa830, usa836s, usa838, usa840, usa842, usa844, usa846, usa848, usa850, usa852, usa854, usa858, usa860, usa862, usa864, usa866, usa868, usa916s, usa918, usa920, usa922, usa924, usa926, usa932s, usa934s, usa936s, usa938s, usa940s, usa942s, usa944s, usa946s, usa952s, usa954s, usa996s, usa1000, usa1040, usa1042, usa1044, usa1052, usa1054, usa1056, usa1068s, usa1070s, usa1072, usa1108, usa1110, usa1124, usa1140, usa1142, usa1178s, usa1204s, usa1254s, usa1256s, usa1258s
- Down Index
- 41of 100
What to do
Check whether you use Salesforce coreService in usa710s, usa712s, usa714, usa716. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4h 26m it lasted.
Anything that failed between 2026-10-08 10:52 UTC and 2026-10-08 15:18 UTC may need a replay.Subscribe to Salesforce's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Salesforce 7
- update
We've identified that new servers are failing to start because required startup files are missing. As a result, we can't add the capacity needed to handle customer traffic, and some customers may experience slow responses or errors. We're reviewing settings and testing fixes on the affected servers. We'll provide an update in 30 minutes, or sooner if we have more information.
provider
- update
We've tested a fix to restore a missing configuration setting on new servers and are preparing to apply it. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- impactradiusincrease
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
provider
- update
We've applied a fix to add a missing configuration setting to affected servers and are restarting them to restore full capacity. Customers may experience a brief increase in background system activity as servers restart. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
As of 15:21 UTC this performance degradation issue has been resolved. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
provider
- update
Upon further investigation, we've determined that the start and end time of impact is different than initially understood. We've revised these times of this Trust post to more accurately reflect the time customers may have experienced impact. We apologize for any confusion caused by this.
provider
- impactradiusincrease
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d593367eb2
Is Salesforce still down?
No, this incident was resolved 2026-10-08 15:18 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
4h 26m, from 2026-10-08 10:52 UTC to 2026-10-08 15:18 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in usa710s, usa712s, usa714, usa716.
What caused it?
Salesforce hasn't published a root cause. If it does, it shows here.
Where does this come from?
Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.