Oregon US7 experienced an issue

Incident Report for OpenText

Postmortem

Incident Report

Tracking number: IM3945745 PM1011644
Incident window: June 16, 2026, from 16:20 GMT to 18:56 GMT
Services affected: OpenText™ Enterprise Service Management (ESM)
RCA target completion date: July 1, 2026

Overview
On June 16, 2026, at 17:19 GMT, Incident Management was engaged to investigate an internal availability Issue impacting ESM SMAX US7.

Impact
Users experienced transaction failures within the Oregon US7 farm, affecting the presales environment and resulting in user inaccessibility.

Resolution
The investigation revealed that platform pods were unable to come online due to readiness probe failures. A controlled rollout restart of platform pods was initiated to continue troubleshooting. This action was intended to be non-disruptive, however, errors occurred which prevented successful pod initialization and contributed to the outage duration. Corrective actions were taken to resolve the messaging failures which enabled platform pods to successfully restart. Service was restored at 18:56 GMT, ending the impact.

‌

Root Cause Analysis

Tracking number: IM3945745 PM1011644
Incident window: June 16, 2026, from 16:20 GMT to 18:56 GMT
Services affected: OpenText™ Enterprise Service Management (ESM)

Overview

On June 16, 2026, at 17:19 GMT, Incident Management was engaged to investigate an internal availability issue impacting ESM SMAX US7.

Impact

Users experienced transaction failures within the Oregon US7 farm, affecting the presales environment and resulting in user inaccessibility.

Root Cause

The investigation revealed that a controlled sequential restart of platform pods was initiated as part of an unrelated diagnostic effort. This action was intended to be non-disruptive; however, errors occurred, preventing successful pod initialization, and the platform pods were unable to come online due to readiness probe failures.

Resolution

Corrective actions were taken to resolve the messaging failures, which enabled platform pods to successfully restart. Service was restored at 18:56 GMT, ending the impact.

Action Plan

Validate whether an earlier identified defect is the root cause of this incident or a separate issue; if separate, define and document the next course of action. - In progress - Target complete September 30, 2026

Posted Jun 18, 2026 - 16:49 UTC

Resolved

Oregon US7 experienced an issue. Clients were unable to access the UI. The issue is now resolved. We appreciate your patience.

Tracking Number: IM3945745
Posted Jun 16, 2026 - 19:05 UTC

Update

Oregon US7 is currently experiencing an issue. Clients are unable to access the UI. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

Tracking Number: IM3945745
Posted Jun 16, 2026 - 18:45 UTC

Investigating

Oregon US7 is currently experiencing an issue. Clients are unable to access the UI. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

Tracking Number: IM3945745
Posted Jun 16, 2026 - 17:44 UTC
This incident affected: Enterprise Service Management (Oregon US7).