Frankfurt EU8 experienced service degradation

Incident Report for OpenText

Postmortem

Incident Report

Tracking number: IM4000627 PM1011731
Incident window: September 17, 2026, from 14:28 GMT to September 17, 2026, at 15:04 GMT
Services affected: OpenText™ Enterprise Service Management (Frankfurt EU8)
RCA target completion date: October 2, 2026

Overview
On September 17, 2026, at 15:17 GMT, Incident Management was engaged to investigate performance degradation affecting OpenText™ Enterprise Service Management clients in the Frankfurt EU8 environment.

Impact
Users experienced performance degradation and reduced system responsiveness while accessing the application.

Resolution
The investigation identified high CPU and memory utilization within the database environment, that contributed to the observed performance delays.

To mitigate the issue and restore service, technical teams created an index for the affected database query to improve query efficiency and executed a controlled restart of the affected deployments. Following these actions, technical teams validated that system performance and stability returned to normal operating thresholds. Full-service recovery was confirmed at 15:40 GMT on September 17, 2026.

Root Cause Analysis

Tracking number: IM4000627 PM1011731
Incident window: September 17, 2026, from 14:28 to 15:04 GMT
Services affected: OpenText™ Enterprise Service Management (Frankfurt EU8)

Overview
On September 17, 2026, at 15:17 GMT, Incident Management was engaged to investigate performance degradation affecting OpenText™ Enterprise Service Management clients in the Frankfurt EU8 environment.

Impact
Users experienced performance degradation and reduced system responsiveness while accessing the application.

Root Cause
The investigation determined that an external integration caused a substantial spike in database utilization, resulting in increased system load and the observed performance degradation.

Resolution
To mitigate the issue and restore service, technical teams created an index for the affected database query to improve query efficiency and executed a controlled restart of the affected deployments. Following these actions, system performance and stability returned to normal operating thresholds at 15:04 GMT, ending the impact. Full-service recovery was confirmed at 15:40 GMT.

Action Plan
Implement code changes and application safeguards to help ensure that excessive load generated by external integrations does not adversely affect the performance and stability of the overall farm. - In progress - Target complete date: Q1 2027

Align with the Global Command Center to enhance monitoring and alerting for abnormal integration traffic, query latency, and connection growth, enabling earlier intervention - Completed

Perform controlled load and resilience testing for high-volume integration scenarios to validate safeguards, alert thresholds, and platform recovery behavior before deployment. - In progress - Target complete date: Q1 2027

Posted Sep 18, 2026 - 16:46 UTC

Resolved

Frankfurt EU8 experienced service degradation. Customers may have experienced intermittent issues accessing the service. The issue is now resolved. We appreciate your patience and understanding.

Tracking Number: IM4000627
Posted Sep 17, 2026 - 15:50 UTC

Investigating

Frankfurt EU8 is currently experiencing service degradation. Customers may experience intermittent issues accessing the service.

Operations, Engineering, and Support teams are actively investigating the issue and working to restore service as quickly as possible. We are treating this as a high priority and will continue to closely monitor the environment while mitigation efforts are in progress.

We appreciate your patience and understanding. We will share more updates as they become available.

Tracking Number: IM4000627
Posted Sep 17, 2026 - 15:29 UTC
This incident affected: Enterprise Service Management (Frankfurt EU8).