Adobe Journey Optimizer Email Delivery Impacted by October 15 Degradation
Adobe reported a global Adobe Journey Optimizer service degradation that began on October 15, 2026, and was resolved early on October 16, 2026. The incident affected customers in the Americas, APAC, and EMEA. Adobe’s official status record listed failed Orchestrated Campaign email deliveries with error messages among the customer impacts. (status.adobe.com)
The incident was part of a broader Adobe Experience Cloud disruption. An independent incident timeline recorded the event as starting at 3:03 PM UTC on October 15 and continuing into October 16, with Adobe Journey Optimizer among the affected services. (pingoru.io)
AJO Services and Customer Impact
Adobe’s affected-service list covered more than a single email delivery subsystem. It included Journey Admin and Configuration, Journey Management, Journey Batch Execution, Journey Unitary Execution, Profile Access Service, Identity Graph Compute for Adobe Experience Platform batch processing, AJO B2C Reporting, and Campaigns Service. The listed scope covered both journey orchestration and supporting profile and identity dependencies. (status.adobe.com)
The documented customer impact was specific to Orchestrated Campaign email deliveries failing with error messages. Adobe did not state that every journey, channel, or campaign type was affected, so the incident should not be generalized beyond the listed services and delivery symptom.
Adobe Attributes Incident to Database Load and Resource Contention
Adobe attributed the service degradation to elevated database load and resource contention in supporting infrastructure. The resolution involved database tuning and other remediation measures, which reduced contention and restored service stability across the affected components. (status.adobe.com)
Teams with Orchestrated Campaign executions during the incident window should reconcile delivery logs, error records, and downstream campaign outcomes. That check is especially important for sends that returned errors, because the status update identifies failed email delivery as the direct AJO customer impact.
