Adobe Journey Optimizer Outage on Sept 17, 2026: 2-Hour Downtime
Highlight text, then choose “Suggest an edit”.Your selection is saved in the bottom bar.
Adobe Journey Optimizer experienced a major availability incident on September 17, 2026, affecting Adobe Experience Cloud and AJO for roughly two hours before service was restored. The Adobe Status page provides the primary service health reference, while IsDown’s incident record separately recorded the event as a resolved major outage.
Adobe Journey Optimizer availability incident affected Experience Cloud
IsDown recorded the incident at 08:54 UTC on September 17 and reported a duration of approximately two hours. Its incident details identify both Adobe Experience Cloud and Adobe Journey Optimizer as affected components and describe the problem as an availability issue under investigation.
The incident was later marked resolved. The available status information does not identify a specific region, customer segment, API, channel, or Journey Optimizer workflow that was affected. That makes the event significant for platform reliability, but it does not establish that every journey, campaign, or message delivery stopped during the incident.
September 17 AJO outage leaves workflow impact unclear
For AJO users, an availability incident can affect more than the authoring interface. Depending on the underlying service involved, teams may see problems opening journeys, loading campaign configuration, processing profile activity, executing actions, or retrieving operational data. The public incident record does not narrow the impact to any of those functions.
That limitation matters when reviewing the event. A platform outage and a failed delivery are not interchangeable. A journey may remain active while a related authoring, orchestration, or reporting dependency is unavailable. Conversely, a short availability interruption can create delayed processing without producing an obvious failure in the user interface.
Another Adobe Journey Optimizer reliability event in September
The September 17 incident is separate from the Adobe Journey Optimizer outage already reported for September 6 and 7. The earlier event lasted 94 minutes, while the new incident was classified as a major availability issue and lasted about two hours.
The recurrence is notable because Adobe Journey Optimizer depends on shared Adobe Experience Cloud and Adobe Experience Platform services. When those dependencies experience availability problems, the effect can extend beyond one journey or campaign and make it harder to isolate whether the failure originated in AJO, platform services, or a connected application layer.
The immediate implication is that September 17 should be treated as a distinct service reliability event, not as a continuation of the earlier outage. Adobe’s public status information confirms the service health context, but additional incident detail is needed to determine which AJO operations were interrupted and whether any customer processing was delayed.
