Salesforce's own status page logged a 19 minute feature degradation hitting Marketing Cloud Engagement on 5 October 2026, starting at 10:02 UTC. Twelve of the platform's 246 tracked components were marked affected, and the fault sits on Salesforce's side.
Started
10:02 UTC
Duration
Lasted 19m
Source
IsDown
Next time
Salesforce is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: DB50241, DB50202, DB50112, DB50129, DB50153, DB50068, DB50169, DB50201, DB50242, DB50268, DB50297, DB50062, DB50050, DB50148, DB50171, DB50248, DB50002, DB50127, DB50265, DB50013, DB50010, DB50006, DB50032, DB50075, DB50014, DB50087, DB50290, DB50211, DB50233, DB50254, DB50099, DB50057, DB50257, DB50142, DB50219, DB50247, DB50011, DB50083, DB50178, DB50020, DB50064, DB50149, DB50272, DB50203, DB50000, DB50007, DB50033, DB50017, DB50040, DB50084, DB50079, DB50130, DB50212, DB50227, DB50274, DB50259, DB50052, DB50018, DB50082, DB50501, DB50065, DB50154, DB50223, DB50267, DB50239, DB50115, DB50036, DB50061, DB50090, DB50086, DB50016, DB50039, DB50066, DB50008, DB50055, DB50088, DB50225, DB50270, DB50214, DB50051, DB50058, DB50160, DB50102, DB50060, DB50056, DB50077, DB50128, DB50197, DB50293, DB50250, DB50001, DB50009, DB50063, DB50114, DB50100, DB50151, DB50187, DB50273, DB50101, DB50190, DB50195, DB50205, DB50215, DB50184, DB50253, DB50264, DB50108, DB50113, DB50037, DB50122, DB50217, DB50251, DB50271, DB50256, DB50012, DB50198, DB50294, DB50230, DB50502, DB50105, DB50296, DB50078, DB50070, DB50226, DB50091, DB50176, DB50229, DB50106, DB50089, DB50177, DB50136, DB50194, DB50004, DB50029, DB50123, DB50022, DB50277, DB50103, DB50207, DB50094, DB50034, DB50107, DB50224, DB50104, DB50208, DB50121, DB50043, DB50074, DB50218, DB50005, DB50030, DB50124, DB50145, DB50220, DB50283, DB50126, DB50026, DB50049, DB50003, DB50027, DB50054, DB50245, DB50031, DB50081, DB50125, DB50170, DB50246, DB50292, DB50235, DB50289, DB50504, DB50295, DB50174, DB50236, DB50097, DB50147, DB50196, DB50181, DB50232, DB50098, DB50038, DB50080, DB50152, DB50193, DB50222, DB50266, DB50073, DB50157, DB50291, DB50053, DB50200, DB50243, DB50015, DB50085, DB50166, DB50244, DB50067, DB50021, DB50221, DB50028, DB50133, DB50173, DB50199, DB50047, DB50163, DB50249, DB50146, DB50172, DB50150, DB50139, DB50175, DB50269, DB50503, DB50238, DB50025, DB50019, DB50076, DB50506, DB50310, DB50307, DB50280, DB50262, DB50304, DB50255, DB50301, DB50209, DB50260, DB50298, DB50109, DB50286, DB50288, DB50508, DB50204, DB50509, DB50513, DB50303, DB50511, DB50516, DB50282, DB50517, DB50518, DB50519, DB50521, DB50522, DB50523, DB50524
What happened?
Salesforce's status page recorded one incident on 5 October 2026, titled "Marketing Cloud Engagement Feature Degradation". It started at 10:02 UTC and lasted 19 minutes. Twelve components were flagged against it, including DB50241, DB50202, DB50112, DB50129, DB50153 and DB50068, out of 246 components Salesforce tracks across the platform. No updates were posted against the incident while it was open, so there is no timeline of diagnosis or mitigation on the record, only the start and the duration. Salesforce did not file any explanation of what caused the degradation or which part of Marketing Cloud Engagement was affected beyond the component list. No user reports were filed during this window, which is consistent with a short, narrow fault that may not have touched most accounts. Over the last 90 days Salesforce has logged 126 incidents with a median duration of 2 hours 30 minutes, so this one resolved well under that typical length. Across all time Salesforce's status page shows 2,460 incidents, giving some sense of how often components across this large a platform report trouble. With zero updates published, the page cannot tell you whether the fix was automatic, manual, or simply the issue clearing on its own. The record only supports what is listed here: the component names, the start time, and the 19 minute duration.
Learning
Marketing Cloud Engagement sits behind a lot of moving parts, and a feature degradation on specific backend components does not always show up as downtime if you are only pinging a login page or a public endpoint. That is the general shape of this kind of fault: narrow enough to hit particular components, short enough that it can start and end inside 19 minutes, and quiet enough that Salesforce filed no updates explaining what broke. Over 30 days UptimeRobot's own checks against Salesforce recorded 32 incidents with a median duration of 2 hours 22 minutes, a different picture from what any single customer's uptime check would show, because external probes and internal feature flags watch different layers of the same system. Your own monitoring tells you whether your integration can reach Salesforce at all. It does not tell you whether a specific feature inside Marketing Cloud Engagement is degraded on Salesforce's end while the API itself stays reachable. That gap is exactly where incidents like this one live. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
