Live  /  OpenText  /  Incident

OpenText: Developer Experience (all locations) is currently experiencing an issue

OpenText · opentext.comCritical outageResolved2026-10-26 21:13 UTC
Public — what happened

Summary

OpenText reported a widespread outage affecting its Developer Experience service in all locations, saying customers could not sign in and therefore could not use it. The problem began on 2026-10-21 at 03:36 UTC, and by 17:31 UTC that day the company said sign-in was working again and it was monitoring. OpenText posted a similar outage notice on 2026-10-26 at 13:10 UTC, then said at 13:51 UTC that access was restored and it was watching for stability. The incident was marked resolved at 21:13 on 2026-10-26, and the company did not state a cause in the text provided.

Affected

Developer Experience - Thrust API Bundle, Developer Experience - Thrust API Bundle, Developer Experience - Thrust API Bundle, Developer Experience - Thrust API Bundle

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 44, 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.