Adobe Marketo Engage Minor Performance Incident on Sept 16
Highlight text, then choose “Suggest an edit”.Your selection is saved in the bottom bar.
Adobe Marketo Engage experienced a minor performance incident on September 16, 2026, lasting about two hours before the service was marked resolved. The public incident records describe a performance issue affecting Marketo Engage and Adobe Experience Cloud, but do not identify a specific feature failure, data center, or API endpoint. (isdown.app)
September 16 Marketo Engage incident was classified as a minor performance issue
The IsDown incident record lists the event as a resolved minor incident and places its duration at approximately two hours. Its incident summary describes Adobe Marketo Engage and Adobe Experience Cloud as experiencing a performance issue that Adobe investigated and resolved. (isdown.app)
The record does not describe the event as a complete platform outage. That distinction matters for teams separating slow or intermittent access from confirmed failures in email delivery, campaign execution, lead processing, or API availability.
Adobe status history places the Marketo Engage issue at 06:15 UTC
HYCU’s Adobe incident history independently records an Adobe Marketo Engage outage beginning at 06:15 UTC on September 16. The same status history shows the incident as resolved, providing a second external record of the disruption and its timing. (it-status.hycu.com)
The timing is relevant for operations teams reviewing activity from that window. A short performance incident can complicate troubleshooting when a campaign appears delayed, a user reports a slow interface, or an integration retry occurs without a clearly documented feature outage. The available records support the existence of a service degradation, but they do not establish that any particular campaign or integration failed.
Public records do not identify a specific Marketo Engage customer impact
Adobe’s public incident details remain limited. Neither external record identifies an affected pod, geographic region, workflow type, or confirmed data integrity issue. As a result, the immediate implication is operational uncertainty rather than evidence of a broad failure across Marketo Engage.
Teams investigating activity from September 16 should distinguish platform performance symptoms from confirmed processing errors in their own instance logs. The incident itself is verified, but claims about missed sends, failed Smart Campaigns, delayed API requests, or lost lead activity would require account-specific evidence that has not been published publicly. (isdown.app)
