Skip to main content
Salesforce

MCGrowth Degradation on CAN40, CAN42, GBR54, GBR70…

Degraded Lasted 2d 18h · started · Salesforce's page

Level
confirmed
Worst impact
Degraded
Components
MCGrowth
Regions
can40, can42, gbr54, gbr70, gbr86, gbr88, jpn134, swe64, swe100, usa316, usa568, usa744, usa846, usa868, usa1052, usa1158, usa1186, usa1212, usa1270
Down Index
43of 100

What to do

  • Check whether you use Salesforce MCGrowth in can40, can42, gbr54, gbr70. 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 2d 18h it lasted.

    Anything that failed between 2026-10-31 00:18 UTC and 2026-11-02 18:49 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 2

  1. update

    During this time, Marketing Starter Pro-Suite customers’ segment-triggered flows may have failed at runtime and not completed their configured actions. The specific impact varies depending on the flow design.

    provider

  2. update

    Our teams have identified the cause of the issue and are actively working on a fix. Thank you for your patience. We'll share another update as soon as we have more information.

    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-015fb94be1

Is Salesforce still down?

No, this incident was resolved 2026-11-02 18:49 UTC. For Salesforce's live state, see https://down.guide/salesforce.

How long did it last?

2d 18h, from 2026-10-31 00:18 UTC to 2026-11-02 18:49 UTC, by the times Salesforce posted.

What was affected?

Salesforce named MCGrowth in can40, can42, gbr54, gbr70.

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.