LoadaView Degradation on 10AZPD, DUB01PD, EW1A, PDANAA…

What to do

• Check whether you use Salesforce LoadaView in 10azpd, dub01pd, ew1a, pdanaa. 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 3d 2h it lasted.

  Anything that failed between 2026-10-13 18:36 UTC and 2026-10-16 21:30 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

1. updateOct 15, 2026, 6:38 AM UTC

   We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Affected customers may experience dashboards and workbooks failing to load, remaining stuck on "Loading data sources," or taking longer than expected to open. To reduce the impact, we disabled a related feature, and we're working on a fix. We don't have an estimated time for resolution yet and we'll provide an update as additional information becomes available.

   provider

2. updateOct 15, 2026, 9:19 AM UTC

   We’ve identified a likely cause related to a recent change that may be causing processes to become deadlocked while loading data sources. We’re working on a code fix to address the suspected cause. Once ready, we’ll test the fix in lower environments before proceeding with production deployment. The previously implemented mitigation of disabling a related feature remains in place to help reduce customer impact. We don’t have an estimated time for resolution yet. We’ll provide another update if additional information becomes available.

   provider

3. impactradiusincreaseOct 15, 2026, 4:42 PM UTC

   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

4. updateOct 15, 2026, 9:28 PM UTC

   We have validated the fix and are working towards production rollout. The earlier mitigation, which disabled a related feature, remains in effect to limit customer impact. There's no estimated resolution time at this point. We'll share another update when more information is available.

   provider

5. updateOct 16, 2026, 1:46 AM UTC

   We've deployed the fix to several instances, and early results are positive. We haven't seen data sources stall when loading in those instances. Deployment to the remaining instances is scheduled for off-peak hours. Customers on instances still awaiting the fix may continue to see data sources stall when loading. We don't have a resolution time yet. We'll provide an update when more information is available.

   provider

6. updateOct 16, 2026, 5:55 AM UTC

   As the fix deployment completes in each region and we restore services, we'll move the resolved instances to a separate Trust post so each resolution time is clear.

   provider

7. updateOct 16, 2026, 11:01 PM UTC

   Deployments have completed in all regions, and services are restored for all impacted customers. 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

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.