Live  /  OpenText  /  Incident

OpenText: Liaison North American clients were experiencing transaction failures.

OpenText · opentext.comResolved2026-11-13 02:02 UTC
Public — what happened

Summary

OpenText said North American customers of several Liaison-related services, including Liaison DXP, EMR Integration, Alloy (NA) and, later, Liaison Service-oriented integration, had transactions fail starting around 20:36 GMT on November 12, 2026. The company said service was restored at 22:15 GMT, while a backlog of documents was still being worked through and new traffic was being held in a queue. OpenText said customers did not need to do anything and that support teams would reprocess affected transactions where possible. No cause was given, and the incident was marked resolved at 02:02 UTC on November 13.

Affected

Alloy NA

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