Live / OpenText / Incident
OpenText: Core US is currently experiencing service degradation
OpenText · opentext.comMinor incidentResolved2026-10-08 23:19 UTC
Public — what happened
Summary
OpenText said search was not working properly in its Core US services starting at 20:00 UTC on 2026-10-08, an incident it rated as minor. The company listed Core Collaboration for Engineering, Core Content Management, the Core Content Management offering for SAP SuccessFactors, and Core Platform - Search as affected. OpenText described the problem as a repeat of an earlier issue but did not give a cause, and it marked the incident resolved at 23:19 the same day.
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 OpenText, Core Platform - Search
Timeline
- Started — 2026-10-08 20:00 UTC
- Identified — 2026-10-08 20:00 UTC (2 updates)
- Resolved — 2026-10-08 23:19 UTC · 3h 19m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach OpenText against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for OpenText: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the OpenText report →
More from OpenText
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.