- Detected by Pingoru
- Mar 05, 2026, 02:59 PM UTC
- Resolved
- Mar 05, 2026, 05:54 PM UTC
- Duration
- 2h 54m
Affected: Zix Encryption Services - ZixPortal
Timeline · 4 updates
-
investigating Mar 05, 2026, 02:59 PM UTC
Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913
-
investigating Mar 05, 2026, 04:17 PM UTC
Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Administrators are unable to configure their portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913
-
investigating Mar 05, 2026, 05:16 PM UTC
Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Administrators are unable to configure their portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913
-
resolved Mar 05, 2026, 05:54 PM UTC
Zix Encryption Services - ZixPortal experienced an issue with the Administrator Console. Administrators were unable to configure their portal. The issue is now resolved. We appreciate your patience. Tracking Number: IM3881913
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 07:54 PM UTC
- Resolved
- Mar 04, 2026, 08:17 PM UTC
- Duration
- 1d
Affected: Zix Customer Portal Interface - Customer Portal
Timeline · 3 updates
-
identified Mar 03, 2026, 07:54 PM UTC
We have an identified an issue with a subset of customers with LDAP imports are unable to log in. We are currently investigating what occurred.
-
monitoring Mar 03, 2026, 10:06 PM UTC
We have restarted LDAP services which will reimport the users. We are currently in the process of restoring back all user/admin settings back to users that were effected. Tracking ID : IM3881037
-
resolved Mar 04, 2026, 08:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 05:42 PM UTC
- Resolved
- Mar 04, 2026, 08:21 PM UTC
- Duration
- 1d 2h
Affected: Zix Customer Portal Interface - ZixCentralZix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE)
Timeline · 3 updates
-
investigating Mar 03, 2026, 05:42 PM UTC
ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) is currently experiencing issues with slow page loads. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3880927
-
monitoring Mar 04, 2026, 04:08 PM UTC
ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced an issue with slow loading pages. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3880927
-
resolved Mar 04, 2026, 08:21 PM UTC
ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced a slow page load issue. The issue is now resolved. We appreciate your patience. Tracking Number: IM3880927
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 06:15 PM UTC
- Resolved
- Mar 28, 2026, 04:47 PM UTC
- Duration
- 25d 22h
Affected: Core Archive for SAP® Solutions - UAE (archive.me.opentext.cloud)
Timeline · 10 updates
-
identified Mar 02, 2026, 06:15 PM UTC
Core Archive UAE is currently experiencing a degraded state due to regional conditions in the Middle East that are impacting our hosting provider’s operations in that area. As a result, customers may experience disruptions across Core Archive functionalities. We are actively collaborating with our hosting provider to mitigate the impact and restore full service as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution.
-
identified Mar 03, 2026, 12:13 PM UTC
Core Archive UAE is currently experiencing an outage due to regional conditions in the Middle East that are impacting our hosting provider’s operations in that area. As a result, customers will experience disruptions across Core Archive functionalities. We are continuing to actively collaborating with our hosting provider to mitigate the impact and restore full service as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution.
-
identified Mar 03, 2026, 01:57 PM UTC
We are continuing to actively collaborating with our hosting provider to mitigate the impact and restore full service as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution.
-
investigating Mar 08, 2026, 06:11 PM UTC
Core Archive UAE (ME) is currently experiencing service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3884136
-
investigating Mar 08, 2026, 06:35 PM UTC
Core Archive UAE (ME) is currently experiencing a degradation of service. The system is back up but will continue to be in degradation state. We are continuing to actively collaborating with our hosting provider to mitigate the impact and restore full service as quickly as possible. We appreciate your patience. Tracking Number: IM3884136
-
investigating Mar 08, 2026, 07:28 PM UTC
Core Archive UAE (ME) is currently experiencing a degradation of service. The system is back up but will continue to be in degradation state. We are continuing to actively collaborate with our hosting provider to mitigate the impact and restore full service as quickly as possible. We appreciate your patience. Tracking Number: IM3884136
-
investigating Mar 09, 2026, 03:30 AM UTC
Core Archive UAE (ME) is currently experiencing a degradation of service. The system is back up but will continue to be in a degraded state. We are continuing to actively collaborate with our hosting provider to mitigate the impact and restore full service as quickly as possible. Updates for this issue will be posted as soon as there are significant updates. We appreciate your patience. Tracking Number: IM3884136
-
investigating Mar 11, 2026, 12:13 PM UTC
Core Archive UAE (ME) is currently experiencing a degradation of service. The system is back up but will continue to be in a degraded state. We are continuing to actively collaborate with our hosting provider to mitigate the impact and restore full service as quickly as possible. Updates for this issue will be posted as soon as there are significant updates. We appreciate your patience. Tracking Number: IM3884136
-
investigating Mar 13, 2026, 12:38 PM UTC
Core Archive UAE (ME) is currently experiencing a degradation of service. The system is back up but will continue to be in a degraded state. We are continuing to actively collaborate with our hosting provider to mitigate the impact and restore full service as quickly as possible. Updates for this issue will be posted as soon as there are significant updates. We appreciate your patience. Tracking Number: IM3884136
-
resolved Mar 28, 2026, 04:47 PM UTC
The Core Archive UAE is currently operational and available. Some users in the region may experience occasional difficulty accessing documents uploaded prior to the start of the incident. We continue to monitor regional conditions in the Middle East, and services remain stable at this time. We will provide additional updates if there are any meaningful changes. If you have any questions or need assistance, please feel free to contact your account executive or reach out to support through your usual channel Tracking Number: IM3884136.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 11:35 PM UTC
- Resolved
- Mar 02, 2026, 12:35 AM UTC
- Duration
- 1h
Affected: Core Archive for SAP® Solutions - IN (archive.in.opentext.cloud)
Timeline · 2 updates
-
investigating Mar 01, 2026, 11:35 PM UTC
We are currently experiencing performance degradation affecting the Core Archive service. Users may notice increased response times or intermittent access delays. Our engineering team is actively investigating and working toward resolution.
-
resolved Mar 02, 2026, 12:35 AM UTC
Core Archive for SAP® Solutions - IN (archive.in.opentext.cloud) experienced service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3879652
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 02:35 PM UTC
- Resolved
- Mar 03, 2026, 03:32 PM UTC
- Duration
- 2d
Affected: Zix Threat Protection - Email Threat Protection
Timeline · 5 updates
-
identified Mar 01, 2026, 02:35 PM UTC
We have identified an issue that is affecting our UK customer base that cannot access their Email Threat Protection logs or quarantine. We are working to resolve this issue as soon as possible. Incident #: IM3879529
-
identified Mar 01, 2026, 10:04 PM UTC
We are continuing to work on resolving this issue with our network teams. Inbound mail flow is unaffected during this time. Incident #: IM3879529
-
identified Mar 02, 2026, 02:13 PM UTC
The networking teams are still working on resolving this issue and are actively troubleshooting and progress is being made. We apologize for any inconvenience this may be causing. Incident #: IM3879529
-
identified Mar 02, 2026, 09:23 PM UTC
Our team is actively working on bringing the server clusters fully back up. Email logs and Quarantine are loading as expected and final items are being restored. Incident #: IM3879529
-
resolved Mar 03, 2026, 03:32 PM UTC
We have restored everything back to normal operational capacity. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 01:22 PM UTC
- Resolved
- Mar 02, 2026, 07:04 PM UTC
- Duration
- 4d 5h
Affected: Core EDR/MDR
Timeline · 10 updates
-
identified Feb 26, 2026, 01:22 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and teams are working to resolve the issue. We appreciate your patience.
-
identified Feb 26, 2026, 02:22 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and are working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 26, 2026, 06:22 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 26, 2026, 10:26 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 27, 2026, 02:22 AM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 27, 2026, 08:32 AM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 27, 2026, 02:22 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Feb 27, 2026, 10:09 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 can experience event logs that may not appear as expected in the portal. All data continues to be processed by the agent. Our engineering team has identified the cause and is working to restore full visibility. The next update will be sent on Monday, March 2, 2026, at 14:00 UTC, or if there are significant updates, whichever comes first. We appreciate your patience.
-
identified Mar 02, 2026, 01:39 PM UTC
Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 can experience event logs that may not appear as expected in the portal. All data continues to be processed by the agent. Our engineering team has identified the cause and is working to restore full visibility. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience.
-
resolved Mar 02, 2026, 07:04 PM UTC
Core EDR/MDR experienced service degradation. The issue is now resolved. We appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 05:29 PM UTC
- Resolved
- Feb 25, 2026, 06:41 PM UTC
- Duration
- 1h 12m
Affected: Zix Encryption Services - Email Message Privacy (EMP)
Timeline · 2 updates
-
investigating Feb 25, 2026, 05:29 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue where notifications are not generated when users send secure email from EMP Web Portal. Secure email notifications (invitation emails, password reset emails, secure email notifications) are not being generated when multiple users send secure emails from the DeliverySlip web portal. Users are unaware of sent secure emails or invitations. US Dallas Site501 (Zix DC) > DB0102 (PROD) Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3876558
-
resolved Feb 25, 2026, 06:41 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) experienced an issue in which notifications are not generated when users send secure email from the EMP Web Portal. Secure email notifications (invitation emails, password reset emails, secure email notifications) are not being generated when multiple users send secure emails from the DeliverySlip web portal. Users are unaware of sent secure emails or invitations. US Dallas Site501 (Zix DC) > DB0102 (PROD). The issue is now resolved. We appreciate your patience. Tracking Number: IM3876558
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 09:28 PM UTC
- Resolved
- Feb 23, 2026, 09:34 PM UTC
- Duration
- 5m
Affected: Zix Customer Portal Interface - Customer Portal
Timeline · 2 updates
-
identified Feb 23, 2026, 09:28 PM UTC
We have identified and working on restoring access to our Customer Portal. We apologize for this inconvenience. IM tracking #: IM3875401
-
resolved Feb 23, 2026, 09:34 PM UTC
We have restored access to the Customer Portal. We apologize for this brief outage.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 07:46 PM UTC
- Resolved
- Feb 18, 2026, 08:31 PM UTC
- Duration
- 45m
Affected: Core Management Console
Timeline · 3 updates
-
investigating Feb 18, 2026, 07:46 PM UTC
Webroot Management Consoles is currently experiencing service degradation and login issues. Teams are currently assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3872780
-
monitoring Feb 18, 2026, 08:27 PM UTC
Webroot Management Consoles experienced service degradation and login issues. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3872780
-
resolved Feb 18, 2026, 08:31 PM UTC
Webroot Management Consoles experienced service degradation and login issues. The issue is now resolved. We appreciate your patience. Tracking Number: IM3872780
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 02:10 PM UTC
- Resolved
- Feb 16, 2026, 03:29 PM UTC
- Duration
- 1h 19m
Affected: Core CommunicationsCore CommunicationsCore Communications
Timeline · 3 updates
-
investigating Feb 16, 2026, 02:10 PM UTC
OpenText is currently experiencing an issue to generate new Exstream licenses. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Communications US - Core Communications Canada - Core Communications Australia Tracking Number: IM3871223
-
identified Feb 16, 2026, 03:15 PM UTC
OpenText is currently experiencing an issue generating new Exstream licenses. The domain has been validated, and teams are working to resolve the issue. We appreciate your patience. - Core Communications US - Core Communications Canada - Core Communications Australia Tracking Number: IM3871223
-
resolved Feb 16, 2026, 03:29 PM UTC
OpenText experienced an issue generating new Exstream licenses. The issue is now resolved. We appreciate your patience. Tracking Number: IM3871223
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 01:30 PM UTC
- Resolved
- Feb 16, 2026, 07:34 PM UTC
- Duration
- 6h 3m
Affected: Zix Hosted Exchange
Timeline · 3 updates
-
investigating Feb 16, 2026, 01:30 PM UTC
Zix - Hosted Exchange (HEX) is currently experiencing an issue with some users unable to access their mailboxes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3871043
-
investigating Feb 16, 2026, 01:34 PM UTC
We are continuing to investigate this issue.
-
resolved Feb 16, 2026, 07:34 PM UTC
Zix - Hosted Exchange (HEX) is resolved. Tracking Number: IM3871043
Read the full incident report →
- Detected by Pingoru
- Feb 15, 2026, 08:41 PM UTC
- Resolved
- Feb 15, 2026, 11:29 PM UTC
- Duration
- 2h 47m
Affected: Core Archive for SAP® Solutions - CH (archive.emea.opentext.com)
Timeline · 5 updates
-
investigating Feb 15, 2026, 08:41 PM UTC
Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955
-
investigating Feb 15, 2026, 09:42 PM UTC
Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams are assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955
-
identified Feb 15, 2026, 10:43 PM UTC
Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955
-
monitoring Feb 15, 2026, 11:20 PM UTC
Core Archive for SAP® Solutions CH (archive.emea.opentext.com) was inaccessible. Service has been restored and monitoring is in progress. We appreciate your patience. Tracking Number: IM3870955
-
resolved Feb 15, 2026, 11:29 PM UTC
Core Archive for SAP® Solutions CH (archive.emea.opentext.com) was inaccessible. The issue is now resolved. We appreciate your patience. Tracking Number: IM3870955
Read the full incident report →
Critical February 15, 2026 - Detected by Pingoru
- Feb 15, 2026, 09:20 AM UTC
- Resolved
- Feb 15, 2026, 09:27 AM UTC
- Duration
- 6m
Affected: Core Archive for SAP® Solutions - NA (archive.na.opentext.com)
Timeline · 2 updates
-
identified Feb 15, 2026, 09:20 AM UTC
Core Archive for SAP® Solutions NA is currently inaccessible. The issue has been identified. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870756
-
resolved Feb 15, 2026, 09:27 AM UTC
Core Archive for SAP® Solutions NA was inaccessible. The issue is now resolved. We appreciate your patience. Tracking Number: IM3870756
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 05:11 AM UTC
- Resolved
- Feb 12, 2026, 05:11 AM UTC
- Duration
- —
Affected: Alloy NA
Timeline · 1 update
-
resolved Feb 12, 2026, 05:11 AM UTC
Alloy North America were unable to send documents. We observed health check failures on our Alloy AS2 server. The issue is now resolved. Please resend transactions that were sent from 11 February 2026 at 11:30 PM GMT. We appreciate your patience. Tracking Number: IM3869001
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 08:34 PM UTC
- Resolved
- Feb 12, 2026, 06:07 AM UTC
- Duration
- 9h 32m
Affected: Core EDR/MDR
Timeline · 6 updates
-
identified Feb 11, 2026, 08:34 PM UTC
Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. We appreciate your patience. Tracking Number: 5196965
-
identified Feb 11, 2026, 09:35 PM UTC
Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. We appreciate your patience. Tracking Number: 5196965
-
identified Feb 11, 2026, 10:34 PM UTC
Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965
-
monitoring Feb 12, 2026, 12:07 AM UTC
Workflows have resumed normal operation; however, the platform is still experiencing partial service degradation. The team is actively monitoring system metrics and performance behavior to ensure stability. Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965
-
monitoring Feb 12, 2026, 03:08 AM UTC
Workflows have resumed normal operation; however, the platform is still experiencing partial service degradation. The team is actively monitoring system metrics and performance behavior to ensure stability. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965
-
resolved Feb 12, 2026, 06:07 AM UTC
Core EDR/MDR operations have returned to normal, and all workflows are running as expected and no further service degradation is observed. This incident is now resolved. Our team will continue to observe post‑recovery metrics to ensure ongoing stability. Tracking Number: 5196965
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 02:57 PM UTC
- Resolved
- Feb 13, 2026, 04:14 PM UTC
- Duration
- 3d 1h
Affected: Zix Hosted Exchange
Timeline · 5 updates
-
investigating Feb 10, 2026, 02:57 PM UTC
Zix - Hosted Exchange (HEX) is currently experiencing an issue with some users unable to access their mailboxes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3867884
-
investigating Feb 10, 2026, 05:20 PM UTC
While access has been restored for many users, some mailboxes are still currently impacted. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3867884
-
investigating Feb 11, 2026, 01:36 PM UTC
Some mailboxes are still experiencing access issues, and we understand the impact this is having. Our teams are treating this as a top‑priority incident and are actively working to resolve the issue as quickly as possible. We sincerely apologize for the continued disruption and appreciate your patience while we work toward resolution. Tracking Number: IM3867884
-
monitoring Feb 12, 2026, 09:08 PM UTC
All users identified as affected by this incident have been notified. Thank you for your patience throughout.
-
resolved Feb 13, 2026, 04:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 01:29 PM UTC
- Resolved
- Feb 09, 2026, 01:13 PM UTC
- Duration
- 2d 23h
Affected: Zix Encryption Services - Email Message Privacy (EMP)
Timeline · 4 updates
-
investigating Feb 06, 2026, 01:29 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with file upload. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3865402
-
identified Feb 06, 2026, 04:38 PM UTC
Zix - Cybersecurity - Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing issues with file uploads and logins. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3865402
-
monitoring Feb 06, 2026, 05:35 PM UTC
Zix - Cybersecurity - Zix Encryption Services - Email Message Privacy (EMP) experienced issues with file uploads and login errors. Service has been restored and is now being validated. We appreciate your patience. Tracking Number:
-
resolved Feb 09, 2026, 01:13 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) experienced issues with file uploads and logins. These issues are now resolved. We appreciate your patience. Tracking Number: IM3865402
Read the full incident report →
Critical February 6, 2026 - Detected by Pingoru
- Feb 06, 2026, 10:09 AM UTC
- Resolved
- Feb 06, 2026, 07:10 PM UTC
- Duration
- 9h 1m
Affected: Core Collaboration for Engineering (xchange.us.opentext.com)Core ComplianceCore Content ManagementCore Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText
Timeline · 4 updates
-
investigating Feb 06, 2026, 10:09 AM UTC
We are currently seeing issues with the following application in Core US. Teams are working towards identifying root cause. Core Collaboration for Engineering (xchange.us.opentext.com) Core Compliance Core Content Management Core Content Management for SAP® SuccessFactors
-
investigating Feb 06, 2026, 10:32 AM UTC
The following applications have been resolved: Core US - Core Collaboration for Engineering (xchange.us.opentext.com) Core US - Core Compliance Teams are still working on resolving the issues with Core US - Core Content Management & Core US - Core Content Management for SAP® SuccessFactors
-
monitoring Feb 06, 2026, 11:42 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 06, 2026, 07:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 04:34 PM UTC
- Resolved
- Feb 05, 2026, 04:34 PM UTC
- Duration
- —
Affected: Core Archive for SAP® Solutions - US (archive.us.opentext.cloud)
Timeline · 1 update
-
resolved Feb 05, 2026, 04:34 PM UTC
Core Archive for SAP® Solutions - US (archive.us.opentext.cloud) experienced an issue that started on 5 February 2026 at 15:30 GMT. Upload/download functionality was unavailable. Service has been restored at 16:00 GMT, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3864715
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 03:33 PM UTC
- Resolved
- Feb 05, 2026, 05:16 PM UTC
- Duration
- 1h 43m
Affected: XM SendSecure - Canada
Timeline · 4 updates
-
investigating Feb 05, 2026, 03:33 PM UTC
XM SendSecure - Canada is currently experiencing an issue. Clients can log in but are unable to send and receive documents. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3864671
-
investigating Feb 05, 2026, 04:30 PM UTC
XM SendSecure - Canada is currently experiencing an issue. Clients can log in but are unable to send and receive documents. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3864671
-
monitoring Feb 05, 2026, 05:08 PM UTC
XM SendSecure - Canada experienced an issue. Clients were unable to send and receive documents. Service has been restored on 5 February 2026 at 16:56 UTC and is now being validated. Any transactions that were sent from 4 February 2026 at 19:00 UTC will need to be resent. We apologize for the inconvenience. Tracking Number: IM3864671
-
resolved Feb 05, 2026, 05:16 PM UTC
XM SendSecure - Canada experienced an issue. Clients were unable to send and receive documents. Service has been restored on 5 February 2026 at 16:56 UTC, and the issue is now resolved. Any transactions that were sent from 4 February 2026 at 00:00 UTC will need to be resent. We apologize for the inconvenience. Tracking Number: IM3864671
Read the full incident report →
