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
Timeline
- Started — 2026-10-21 03:36 UTC
- Investigating — 2026-10-21 03:36 UTC
- Monitoring — 2026-10-21 17:31 UTC
- Identified — 2026-10-26 13:10 UTC
- Monitoring — 2026-10-26 13:51 UTC
- Resolved — 2026-10-26 21:13 UTC · 6 days 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 44, 2026, our weekly internet health report.