OpenText experienced a minor incident on June 16, 2026 affecting Oregon US7, lasting 1h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 16, 2026, 05:44 PM UTC
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
- investigating Jun 16, 2026, 06:45 PM UTC
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
- resolved Jun 16, 2026, 07:05 PM UTC
Oregon US7 experienced an issue. Clients were unable to access the UI. The issue is now resolved. We appreciate your patience. Tracking Number: IM3945745
- postmortem Jun 18, 2026, 04:25 PM UTC
# **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.