Adobe Journey Optimizer outage lasted 94 minutes across September 6 and 7
The latest Adobe Journey Optimizer outage was reported on September 7, 2026, after a 94-minute incident that began at 11:12 p.m. UTC on September 6 and ended at 12:47 a.m. UTC on September 7. Pingoru’s outage history listed both Adobe Journey Optimizer and Platform Core Services among the affected components and classified the event as a notice. (pingoru.io)
Adobe Journey Optimizer incident affected Platform Core Services
A separate PulsAPI incident log recorded the same September 6 event as a resolved Adobe Journey Optimizer incident lasting 1 hour and 34 minutes. The matching start date, duration, and affected platform service provide independent confirmation that the disruption was tied to shared Adobe infrastructure rather than an isolated customer configuration problem. (pulsapi.com)
That distinction matters because Adobe Journey Optimizer is built on Adobe Experience Platform. A platform-level service issue can therefore affect more than the visible journey canvas, depending on which underlying service is degraded. Adobe’s Journey Optimizer product description identifies the product’s real-time journey orchestration capabilities as part of the Experience Platform architecture. (helpx.adobe.com)
What the September 7 AJO outage meant for journey operations
The public incident records do not identify which specific AJO capabilities experienced errors or delays. It would therefore be inaccurate to claim that every journey, campaign, or message delivery was affected. The immediate implication is narrower: teams working in AJO during the incident window could have encountered temporary problems in operations that depended on Platform Core Services, including journey authoring, publishing, profile processing, or reporting.
For teams investigating failed actions or unexpected delays around the outage window, the timing is important. Errors recorded between 11:12 p.m. UTC on September 6 and 12:47 a.m. UTC on September 7 may have been related to the platform incident rather than to journey logic, audience configuration, or channel setup. Both monitoring records show the incident as resolved, with no indication in the available reports of a permanent product change. (pulsapi.com)
Share With Others
Platinum
