OpenText incident
Core Archive for SAP® Solutions CH was inaccessible
Affected components
Update timeline
- 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
Looking to track OpenText downtime and outages?
Pingoru polls OpenText's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when OpenText reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track OpenText alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required