Adobe Marketo Engage Fixes Major Outage Caused by Credential Error
Adobe Marketo Engage resolved a major service disruption on September 29, 2026, after a database credential configuration issue caused authentication failures for a subset of customers. Adobe said affected users may have been unable to log into the application and may have encountered errors with certain services and APIs. The independent incident record from IsDown also recorded the event as a resolved major outage affecting Adobe Marketo Engage and Adobe Experience Cloud. (status.adobe.com)
Authentication Failures Affected Marketo Services and Integrations
Adobe’s status update identified the affected service areas as the Munchkin API, forms, SOAP API, and third-party CRM, API, and LaunchPoint connections. The incident affected a subset of Adobe Marketo Engage customers globally, with the published environment list covering multiple Ashburn pods. (status.adobe.com)
Adobe marked the incident closed after its engineering team corrected the database credential configuration. The public update does not report data loss, changes to customer configuration, or a required customer-side remediation.
Teams that saw Marketo login failures, form errors, Munchkin activity problems, SOAP failures, or CRM and LaunchPoint errors during the incident window should compare those timestamps with their own application and integration logs before changing credentials, endpoints, or campaign logic. The documented cause was an Adobe-side authentication configuration issue, not a confirmed customer integration defect.
Marketo Admins Can Subscribe to Environment-Specific Status Alerts
Marketo administrators can use Adobe’s system status notification instructions to subscribe to Adobe Marketo Engage events by data center, pod, service, and event type. That setup is particularly useful for teams operating CRM sync, forms, Munchkin, SOAP, or LaunchPoint integrations that need to distinguish a platform incident from an implementation problem. (experienceleague.adobe.com)
