Adobe Journey Optimizer EMEA Outage on October 12, 2026: 2-Hour Service Degradation
Adobe Journey Optimizer experienced an EMEA service degradation on October 12, 2026, delaying journey execution for journeys using wait nodes. The incident ran from 6:45 PM to 8:51 PM GMT and was marked closed after processing resumed. Adobe’s official status record identifies Journey Orchestration, specifically Journey Batch Execution, as the affected service. (status.adobe.com)
An independent incident log from IsDown recorded the same event as a resolved minor outage lasting approximately two hours, matching Adobe’s reported incident window. (isdown.app)
Wait-node journey execution was the affected area
The documented impact applied to a subset of Adobe Journey Optimizer customers in the EMEA region. Customers may have experienced delayed execution in journeys containing wait nodes, while Adobe’s resolution summary states that journey processing resumed as expected and the identified processing delays were addressed.
The incident record does not describe a configuration change, channel failure, or audience processing issue. Its scope is limited to delayed journey execution within Journey Batch Execution, making the timing of profile progression the main implementation concern.
Checks for affected AJO teams
Teams supporting EMEA journeys should review execution logs and profile progression for journeys with wait nodes during the 6:45 PM to 8:51 PM GMT incident window. Comparing expected wait completion times with actual activity timestamps can help distinguish delayed platform execution from issues involving audience qualification, decisioning, or channel configuration.
