Adobe Marketo Engage Restores Major San Jose Service Disruption
Highlight text, then choose “Suggest an edit”.Your selection is saved in the bottom bar.
Adobe Marketo Engage experienced a major service disruption in the San Jose region on September 24, 2026, affecting login access and services listed by Adobe as forms, the Munchkin API, SOAP API, and third-party CRM and LaunchPoint connections. Adobe later marked the incident resolved after engineering teams restored normal service. Adobe’s System Status record identifies the incident as issue 202609230103. (status.adobe.com)
San Jose incident affected Marketo APIs, forms, and LaunchPoint services
The disruption began at 2:15 a.m. GMT and ended at 3:55 a.m. GMT, with Adobe posting its resolution update at 4:11 a.m. GMT. The incident was classified as a major issue affecting some customers in the Americas, specifically across San Jose Marketo environments. Adobe’s update said affected customers may have experienced problems logging in to Adobe Marketo Engage. (status.adobe.com)
The affected-service list covered more than the Marketo user interface. It included marketing automation activities involving forms, the Munchkin API, SOAP API, and third-party CRM, APIs, and LaunchPoint services. The public incident record does not identify a root cause or describe any data loss.
An independent status monitor also recorded a resolved Adobe Marketo Engage outage beginning at 2:15 a.m. UTC on September 24 and lasting approximately two hours, matching Adobe’s published incident window. (isdown.app)
The notice applies to the San Jose region. It does not establish that Ashburn, Amsterdam, Sydney, London, or other Marketo data centers were affected. Teams that experienced errors during the window should review login attempts, form activity, API responses, SOAP integrations, and LaunchPoint logs against their own timestamps before assuming that individual configuration changes caused the failure.
