Live  /  OpenText  /  Incident

OpenText: Desktop Messaging BMS is currently experiencing failures in processing PDF files

OpenText · opentext.comMinor incidentResolved2026-10-17 02:16 UTC
Public — what happened

Summary

OpenText said its Desktop Messaging BMS service was failing to process PDF files, starting at 21:08 UTC on 2026-10-16. Later updates, from 23:48 UTC, described the problem as delays in PDF processing rather than outright failures. OpenText said teams were working on it throughout and did not state a cause in its updates. The incident is marked resolved as of 02:16 UTC on 2026-10-17.

Affected

Desktop Messaging BMS

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