Core Collaboration for Engineering (xchange.us.opentext.com)Core Content Management (corecontent.us.opentext.com)Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenTextCore Content Management
investigating
The following services are currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
Tracking Number: IM4021979
monitoring
The following services were unavailable. Services have been restored and are now being validated. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
Tracking Number: IM4021979
resolved
The following services were unavailable. The issue is now resolved. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
Tracking Number: IM4021979
Developer Experience (all locations) is currently experiencing an issue
Started October 21, 2026 at 3:36 AM UTC · 5d 17h
OutageCritical incident
Affected components
Developer Experience - Thrust API BundleDeveloper Experience - Thrust API BundleDeveloper Experience - Thrust API BundleDeveloper Experience - Thrust API Bundle
investigating
We are currently experiencing a widespread service outage impacting Developer Experience across all locations. Customers are unable to authenticate, preventing access to the service. Our technical teams are actively investigating the issue and working to restore normal operations as quickly as possible. Further updates will be provided as more information becomes available.
Reference: IM4021478
identified
We are currently experiencing a widespread service outage impacting Developer Experience across all locations. Customers are unable to authenticate, preventing access to the service. Our technical teams are actively investigating the issue and working to restore normal operations as quickly as possible. Further updates will be provided as more information becomes available.
monitoring
The authentication issue impacting Developer Experience across all locations has been resolved, and customer access has been restored. Our technical teams are continuing to closely monitor the environment to ensure service stability and prevent further disruptions.
resolved
The authentication issue impacting Developer Experience across all locations has been fully resolved, and normal service operations have been restored. Following continued monitoring, the environment has remained stable with no further disruptions observed. The incident is now considered resolved and officially closed.
Multiple Applications in OCP North America and Europe were unavailable
Started October 18, 2026 at 5:11 AM UTC · 1d 1h
Pending
resolved
The following applications in both North America (Li3) and Europe (AM3) were unavailable. Teams were assembled at the time and recoveries were seen after restarting Authentication and Entitlement services.
Core Content
Core for Success Factors
Core Federated Compliance
Core Collaboration for Engineering (Supplier Exchange)
Reference: IM4019859
Desktop Messaging BMS was experiencing failures in processing PDF files
Started October 16, 2026 at 9:08 PM UTC · 5h 8m
IssuesMinor incident
Affected components
Desktop Messaging BMS
investigating
Desktop Messaging BMS is currently experiencing failures in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4019383
investigating
Desktop Messaging BMS is currently experiencing delays in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4019383
resolved
Desktop Messaging BMS was experiencing delays in processing PDF files. The issue is now resolved. We appreciate your patience.
Tracking Number: IM4019383
Core Management Console is currently experiencing intermittent login failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4019194
resolved
Core Management Console experienced intermittent login failures. The issue is now resolved. We appreciate your patience.
Tracking Number: IM4019194
RCA for IM4000627 PM1011731
Started October 12, 2026 at 5:50 PM UTC · 0m
Pending
Affected components
Frankfurt EU8
resolved
The RCA is now available. Click here for RCA.
RCA for IM3998323 PM1011731
Started October 12, 2026 at 5:45 PM UTC · 0m
Pending
Affected components
Frankfurt EU8
resolved
The RCA is now available. Click here for RCA.
Zix SMB and Secure Cloud Encryption services Receiving "Unbalanced" reject for outgoing messages
Multiple services are currently experiencing an issue where senders of messages are receiving "unbalanced" as a reject/NDR notification.
Teams are currently assembled and working to resolve the issue.
We appreciate your patience.
Tracking Number: forth coming
investigating
Multiple services are currently experiencing an issue in which message senders are receiving "unbalanced" as a reject/NDR notification.
Teams are currently assembled and working to resolve the issue.
We appreciate your patience.
Tracking Number: IM4015057
investigating
Zix SMB and Secure Cloud Encryption services are currently experiencing an issue when senders of messages are receiving a reject notice/NDR with "Unbalanced" as the reason.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4015057
investigating
Zix SMB and Secure Cloud Encryption Services are still experiencing an issue when sending outbound messaging.
Teams have assembled, identified the problem, and are working to resolve the issue as quickly as possible. We appreciate your patience.
Tracking Number: IM4015057
monitoring
Zix SMB and Secure Cloud Encryption services experienced an issue where all outbound messages were rejected for "Unbalanced".
Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM4015057
resolved
Zix SMB and Secure Cloud Encryption services experienced an issue when sending outbound messages. Users would experience messages being undelivered, with the NDR showing the issue as Unbalanced.
The issue is now resolved. We appreciate your patience.
Tracking Number: IM4015057
Core Share CA Login Issue
Started October 8, 2026 at 10:29 PM UTC · 5m
OutageMajor incident
Affected components
Core Share - CA
investigating
We are currently investigating this issue.
investigating
Issue has been resolved. Core Share CA is fully operational.
resolved
This incident has been resolved.
Core US was experiencing service degradation
Started October 8, 2026 at 8:00 PM UTC · 3h 19m
IssuesMinor incident
Affected components
Core Collaboration for Engineering (xchange.us.opentext.com)Core Content Management (corecontent.us.opentext.com)Core Platform - SearchCore Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
identified
Core US is currently experiencing an issue affecting search functionality. Teams have identified a recurrence and are working to resolve the issue. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Tracking Number: IM4014044
identified
Core US is currently experiencing an issue affecting search functionality. Teams have identified a recurrence and are working to resolve the issue. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Updates for this issue will be sent every 2 hours or if there are any significant updates, whichever comes first.
Tracking Number: IM4014044
resolved
Core US was experiencing an issue affecting search functionality. The issue is now resolved. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Tracking Number: IM4014044
Core US experienced service degradation
Started October 8, 2026 at 12:37 AM UTC · 3h 17m
IssuesMinor incident
Affected components
Core Collaboration for Engineering (xchange.us.opentext.com)Core Content Management (corecontent.us.opentext.com)Core Platform - SearchCore Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
investigating
We are currently experiencing an issue affecting the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC.
Impacted Applications:: Core Content / Core4SF / Core Collaboration for Engineering
Documents uploaded prior to the specified date and time should remain fully searchable and unaffected by this issue.
Our technical teams are actively engaged and working together to identify the root cause and restore normal search functionality as quickly as possible.
We apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution. Additional updates will be provided as more information becomes available.
identified
Core US is currently experiencing service degradation. This issue is affecting the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC.
Documents uploaded prior to the specified date and time should remain fully searchable and unaffected by this issue.
Our technical teams are actively engaged and working together to identify the root cause and restore normal search functionality as quickly as possible.
We apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution. Additional updates will be provided as more information becomes available.
monitoring
Core US experienced service degradation. This issue affected the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. The queues are currently draining and being monitored. Service has been restored and is being validated. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Tracking Number: IM4014044
monitoring
Core US experienced service degradation. This issue affected the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. The queues are currently draining and being monitored. Service has been restored and is being validated. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Updates for this issue will be posted as soon as there are significant updates.
resolved
Core US experienced service degradation. The issue is now resolved. We appreciate your patience.
- Core Collaboration for Engineering (xchange.us.opentext.com)
- Core Content Management (corecontent.us.opentext.com)
- Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
- Core Platform - Search
Tracking Number: IM4014044
Zix - Hosted Exchange Some users may receive Error 500 when accessing OWA
Started October 7, 2026 at 1:53 PM UTC · 6h 3m
IssuesMinor incident
Affected components
Zix Hosted Exchange
investigating
Zix - Hosted Exchange some users are currently experiencing an issue accessing OWA, receiving an error 500. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4013681
monitoring
Zix - Hosted Exchange some users are currently experiencing an issue accessing OWA, receiving an error 500.. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM4013681
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved.
Frankfurt EU38 experienced an issue
Started October 2, 2026 at 5:00 PM UTC · 0m
Pending
Affected components
Frankfurt EU38
resolved
Frankfurt EU38 experienced an issue with Integration Studio. Saving listeners and creating scenarios were not working. The issue is now resolved. We appreciate your patience.
Tracking Number: 3349552
Core Archive for SAP® Solutions - DE and Core Archive for SAP® Solutions - AU were unavailable
Started October 1, 2026 at 9:46 AM UTC · 32m
OutageMajor incident
Affected components
Core Archive for SAP® Solutions - DE (archive.de.opentext.cloud)Core Archive for SAP® Solutions - AU (archive.au.opentext.cloud)
investigating
Core Archive for SAP® Solutions - DE and Core Archive for SAP® Solutions - AU are currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4009632
resolved
Core Archive for SAP® Solutions - DE and Core Archive for SAP® Solutions - AU were unavailable. The issue is now resolved. We appreciate your patience.
Tracking Number: IM4009632
Core Capture EU is experiencing degraded performance
Started September 30, 2026 at 3:17 PM UTC · 7d 9h
IssuesMinor incident
Affected components
Core Capture for SAP® Solutions
investigating
We are currently investigating an issue causing processing slowness for clients within the Core Capture GCP-EU environment. Our technical teams are actively working to identify the cause and restore normal processing as quickly as possible.
We will provide additional updates as more information becomes available.
identified
Our technical teams have identified a potential cause for the processing slowness and are currently conducting tests to validate the findings and confirm a path forward for remediation.
We will provide a further update as testing progresses and additional information becomes available.
monitoring
A fix has been implemented, and initial testing has shown improved processing performance. Our technical teams continue to closely monitor the environment to confirm processing remains stable.
We will provide further updates as monitoring continues.
investigating
We are seeing a recurrence of the processing slowness impacting clients within the Core Capture GCP-EU environment. Our technical teams are actively investigating the issue and working to restore normal processing as quickly as possible.
We will provide additional updates as more information becomes available.
monitoring
At this time, we are no longer observing processing slowness, and the system has returned to normal processing speeds.
Our technical teams continue to work with our vendor to identify any potential latency that may be introduced at the network or other service layers.
Customers should expect normal processing performance. If you experience any further slowness, please follow the standard reporting process to report the issue so that our teams can investigate promptly.
monitoring
We continue to work closely with our vendor to investigate the ongoing performance issue. The system is currently experiencing slower-than-normal processing, but transactions are continuing to be processed at this time.
Our teams remain actively engaged and are working to restore normal processing speeds. We will provide additional updates as more information becomes available.
monitoring
We have applied several fixes that have resulted in improved processing performance within the Core Capture GCP-EU environment. Our teams continue to work closely with the vendor to address the remaining performance concerns and bring the issue to a complete resolution.
We will provide further updates as progress continues.
Customers should expect normal processing performance. If you experience any further slowness, please follow the standard reporting process to report the issue so that our teams can investigate promptly.
resolved
This incident has been resolved.
Core EDR/MDR experienced service degradation
Started September 25, 2026 at 6:56 PM UTC · 0m
Pending
Affected components
Core EDR/MDR
resolved
Core EDR/MDR experienced an issue affecting workflow processing. Workflows created on or after 11 September 2026, as well as existing workflows updated on or after that date, may have not been triggering as expected. The issue is now resolved. We appreciate your patience.
If you have any questions or concerns, please reach out to the Support Team.
Core DNS Protection Block Page experienced an issue
Started September 23, 2026 at 8:10 PM UTC · 5d 20h
IssuesMinor incident
Affected components
Core DNS Protection
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. We appreciate your patience.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent on 28 September 2026 or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first.
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams have scheduled the required DNS Agent update to begin today, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
The required DNS Agent update, and a related client utility update is in progress. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent by 1:00 PM Eastern tomorrow, or if there are significant updates, whichever comes first.
Tracking Number: I5791953
resolved
Core DNS Protection Block Page clients experienced an issue accessing blocked HTTPS websites. The required updates are now available and should be applied automatically soon. Once completed, the issue is expected to be resolved without further action. The related certificate deployment utility is also available for download. We appreciate your patience.
Tracking Number: I5791953
CTIS Service was in a degraded state in OCP US
Started September 18, 2026 at 3:11 PM UTC · 2h 19m
IssuesMinor incident
Affected components
Core Platform - Content Transformation and Injection ServicesCore Capture (corecapture.us.opentext.com)
investigating
Customers using CTIS-based ingestion in the OCP US environment may experience delays processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are assembled and actively looking at the issue for root cause and remediation
Reference: IM4001177
investigating
We are continuing to investigate this issue.
investigating
Customers using CTIS-based ingestion in the OCP US environment may experience delays in processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4001177
monitoring
CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM4001177
resolved
CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. The issue is now resolved. We appreciate your patience.
Tracking Number: IM4001177
Frankfurt EU8 experienced service degradation
Started September 17, 2026 at 3:29 PM UTC · 21m
IssuesMinor incident
Affected components
Frankfurt EU8
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
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
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**
Frankfurt EU8 experienced a service degradation.
Started September 14, 2026 at 1:35 PM UTC · 41m
IssuesMinor incident
Affected components
Frankfurt EU8
investigating
Frankfurt EU8 is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3998323
monitoring
Frankfurt EU8 experienced a service degradation. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM3998323
resolved
Frankfurt EU8 experienced a service degradation. The issue is now resolved. We appreciate your patience.
Tracking Number: IM3998323
postmortem
# **Incident Report**
**Tracking number:** IM3998323 PM1011731
**Incident window:** September 14, 2026, from 12:32 GMT to 13:35 GMT
**Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\)
**RCA target completion date:** August 29, 2026
**Overview**
On September 14, 2026, at 13:31 GMT, Incident Management was engaged to investigate service degradation affecting the OpenText™ Enterprise Service Management.
**Impact**
Several customers experienced performance degradation while using the OpenText™ Service Management \(SMAX\) application. The product UI was slow to resolve during this period for impacted customers and some logins were delayed.
**Resolution**
The investigation determined that a database spike initiated by an external integration resulted in the observed performance degradation.
The integration was paused to reduce impact on the database and the system automatically. Performance stabilized at 13:35 GMT on September 14, 2026. OpenText has followed up on the integration with impacted customers to ensure best practices for use are followed going forward.
# **Root Cause Analysis**
**Tracking number:** IM3998323 PM1011731
**Incident window:** September 14, 2026, from 12:32 GMT to 13:35 GMT
**Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\)
**Overview**
On September 14, 2026, at 13:31 GMT, Incident Management was engaged to investigate service degradation affecting the OpenText™ Enterprise Service Management \(Frankfurt EU8\).
**Impact**
Several customers experienced performance degradation while using the OpenText™ Service Management \(SMAX\) application. The product UI was slow to resolve during this period for impacted customers, and some logins were delayed.
**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**
The integration was paused to reduce database and system load. Performance stabilized, and normal operations resumed at 13:35 GMT on September 14, 2026.
**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**
Engage the customer responsible for the external integration to review best practices around configuration and operation to help minimize performance impact on the platform. **- Completed**
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**