Live  /  OpenText  /  Incident

OpenText: Core US experienced service degradation

OpenText · opentext.comMinor incidentResolved2026-10-08 03:53 UTC
Public — what happened

Summary

OpenText reported a minor problem in its Core US region, beginning at 00:37 UTC on October 8, 2026, in which documents uploaded from 11:00 AM UTC on October 2, 2026 onward could not be found through search, while older files stayed searchable. The company listed Core Content Management, Core Collaboration for Engineering, its SAP SuccessFactors document management offering and Core Platform Search as affected. OpenText moved the issue to identified at 01:20 UTC but did not publicly name a cause, and by 02:11 UTC said search was working again while backed-up processing queues cleared. The incident was marked resolved at 03:53 UTC.

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

As listed on OpenText’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the OpenText status & history page.

Related: OpenText status & history. SquidGrid is not affiliated with OpenText.