OpenText incident

Desktop Messaging BMS experienced a degradation in service

Minor Resolved View vendor source →

OpenText experienced a minor incident on June 17, 2026 affecting Desktop Messaging BMS, lasting 2h 52m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 01:17 PM UTC
Resolved
Jun 17, 2026, 04:10 PM UTC
Duration
2h 52m
Detected by Pingoru
Jun 17, 2026, 01:17 PM UTC

Affected components

Desktop Messaging BMS

Update timeline

  1. investigating Jun 17, 2026, 01:17 PM UTC

    Clients are unable to log into the faxadmin portal and experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

  2. investigating Jun 17, 2026, 02:17 PM UTC

    Desktop Messaging BMS is experiencing a degradation in service. Clients are unable to log in to the faxadmin portal and are experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

  3. investigating Jun 17, 2026, 03:17 PM UTC

    Desktop Messaging BMS is experiencing a degradation in service. Clients are unable to log in to the faxadmin portal and are experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

  4. resolved Jun 17, 2026, 04:10 PM UTC

    Desktop Messaging BMS experienced a degradation in service. Clients were unable to log in to the faxadmin portal and are experiencing SOAP API query errors. The issue is now resolved. We appreciate your patience. Tracking Number: IM3946292