- 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 →
- Detected by Pingoru
- Jan 29, 2026, 09:46 PM UTC
- Resolved
- Jan 29, 2026, 09:46 PM UTC
- Duration
- —
Affected: Core Messaging - Email
Timeline · 1 update
-
resolved Jan 29, 2026, 09:46 PM UTC
Core Messaging - Email may have experienced intermittent message delivery delays, which started on 23 January 2026 at 05:00 UTC. Service has been restored on 29 January 2026 at 21:41 UTC. The issue is now resolved. We appreciate your patience. Tracking Number: IM3859146
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 03:43 PM UTC
- Resolved
- Jan 29, 2026, 09:18 PM UTC
- Duration
- 5h 35m
Affected: Zix Support Infrastructure - Support Ticketing System
Timeline · 3 updates
-
investigating Jan 29, 2026, 03:43 PM UTC
Email to our ticketing system is currently experiencing issues with long delays. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: OTSM 51714775
-
monitoring Jan 29, 2026, 05:55 PM UTC
Email to our ticketing system experienced an issue with long delays. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: OTSM 51714775
-
resolved Jan 29, 2026, 09:18 PM UTC
Email to our ticketing system experienced an issue with long delays. The issue is now resolved. We appreciate your patience. Tracking Number: OTSM 51714775
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 02:33 PM UTC
- Resolved
- Jan 29, 2026, 04:03 PM UTC
- Duration
- 1h 29m
Affected: B2B ConnectCore Collaboration AccessCore Secure AccessProviderLinkSupplier ConnectionSupplier Portal
Timeline · 4 updates
-
investigating Jan 29, 2026, 02:33 PM UTC
The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358
-
investigating Jan 29, 2026, 03:30 PM UTC
The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358
-
monitoring Jan 29, 2026, 03:51 PM UTC
The following services experienced an issue and have been restored. - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging was not impacted. - Supplier Connection login and UI; messaging was not impacted. - Supplier Portal Core Secure Access and Core Collaboration Access are still being validated. We appreciate your patience. Tracking Number: IM3860358
-
resolved Jan 29, 2026, 04:03 PM UTC
The following services experienced an issue and have all been restored. The issue is now resolved. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 07:59 PM UTC
- Resolved
- Jan 23, 2026, 01:01 PM UTC
- Duration
- 17h 1m
Affected: Zix Office 365
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 08:15 PM UTC
- Resolved
- Jan 20, 2026, 09:44 PM UTC
- Duration
- 1h 29m
Affected: 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 Digital Asset Management (coredam.us.opentext.com)
Timeline · 3 updates
-
investigating Jan 20, 2026, 08:15 PM UTC
Core US is currently degraded. Teams are being assembled to investigate and provide resolution.
-
monitoring Jan 20, 2026, 08:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 20, 2026, 09:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 10:34 PM UTC
- Resolved
- Jan 14, 2026, 01:41 AM UTC
- Duration
- 3h 7m
Affected: Core Fax - US
Timeline · 6 updates
-
investigating Jan 13, 2026, 10:33 PM UTC
Core Fax Canada and North America are experiencing degradation in service. Backlogs exists. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319
-
investigating Jan 13, 2026, 10:34 PM UTC
Core Fax North America only is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319
-
investigating Jan 13, 2026, 10:51 PM UTC
Core Fax North America is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319
-
investigating Jan 13, 2026, 11:37 PM UTC
Core Fax North America is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. We appreciate your patience. We appreciate your patience. Tracking Number: IM3851319
-
investigating Jan 14, 2026, 01:40 AM UTC
Core Fax North America was experiencing degradation in service. Backlogs have been cleared. The issue is now resolved. We appreciate your patience. Tracking Number: IM3851319
-
resolved Jan 14, 2026, 01:41 AM UTC
Core Fax North America was experiencing degradation in service. Backlogs have been cleared. The issue is now resolved. We appreciate your patience. Tracking Number: IM3851319
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 02:53 PM UTC
- Resolved
- Jan 12, 2026, 11:52 PM UTC
- Duration
- 8h 59m
Affected: Zix Encryption Services - Email Message Privacy (EMP)
Timeline · 4 updates
-
investigating Jan 12, 2026, 02:53 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with some US domains receiving an error when composing a secure message. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number:
-
investigating Jan 12, 2026, 02:53 PM UTC
(Updated Tracking Number) Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with some US domains receiving an error when composing a secure message. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3849179
-
monitoring Jan 12, 2026, 04:26 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with some US domains receiving an error when composing a secure message. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3849179
-
resolved Jan 12, 2026, 11:52 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with some US domains receiving an error when composing a secure message. The issue is now resolved. We appreciate your patience. Tracking Number: IM3849179
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 04:04 PM UTC
- Resolved
- Jan 12, 2026, 03:01 PM UTC
- Duration
- 5d 22h
Affected: Zix Encryption Services - Email Message Privacy (EMP)
Timeline · 3 updates
-
investigating Jan 06, 2026, 04:04 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with Australian users having issues composing secure messages. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3846958
-
investigating Jan 08, 2026, 05:55 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) is still experiencing an issue with Australian users having issues composing secure messages. Teams have assembled and are working to resolve the issue. We appreciate your patience. Tracking Number: IM3846958
-
resolved Jan 12, 2026, 03:01 PM UTC
Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with Australian users having issues composing secure messages. The issue is now resolved. We appreciate your patience. Tracking Number: IM3846958
Read the full incident report →
- Detected by Pingoru
- Dec 06, 2025, 01:55 PM UTC
- Resolved
- Jan 29, 2026, 05:31 PM UTC
- Duration
- 54d 3h
Affected: Desktop Messaging BMSDesktop Messaging BMSDesktop Messaging BMSFax Cloud Connect (RightFax)Fax Cloud Connect (RightFax)Fax2MailFax2Mail
Timeline · 43 updates
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 07:45 PM UTC
- Resolved
- Jan 21, 2026, 01:55 PM UTC
- Duration
- 50d 18h
Affected: Zix Encryption Services - ZixPortal
Timeline · 7 updates
Read the full incident report →