Hyland incident

Increased error rates have been identified

Major Resolved View vendor source →

Hyland experienced a major incident on April 11, 2025 affecting Ashburn, USA (IAD) and Sydney, Australia (SYD) and 1 more component, lasting 2h 22m. The incident has been resolved; the full update timeline is below.

Started
Apr 11, 2025, 05:27 PM UTC
Resolved
Apr 11, 2025, 07:49 PM UTC
Duration
2h 22m
Detected by Pingoru
Apr 11, 2025, 05:27 PM UTC

Affected components

Ashburn, USA (IAD)Sydney, Australia (SYD)AWS Frankfurt (AMS/QEF)Melbourne, Australia (MEL)Boyers, USA (PIT)London, UK (LHR)Auckland, New Zealand (AKL)Toronto, Canada (D01)Kansas City/AWS East, USA (ARSL)AWS Northern Virginia (AWVA)

Update timeline

  1. investigating Apr 11, 2025, 05:27 PM UTC

    Hyland is aware of increased error rates. Hyland is engaged and investigating this issue with the highest priority. Additional details will be provided as they become available.

  2. identified Apr 11, 2025, 05:37 PM UTC

    Hyland has identified an issue with Citrix and is working towards a resolution.

  3. identified Apr 11, 2025, 07:04 PM UTC

    Hyland has identified the issue with Citrix and are still working on the remediation with the highest priority. Additional details will be provided as they become available.

  4. monitoring Apr 11, 2025, 07:32 PM UTC

    Hyland believes the issue is resolved. We are still actively monitoring.

  5. monitoring Apr 11, 2025, 07:38 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 11, 2025, 07:49 PM UTC

    Hyland has remediated the issue. If you continue to have any issues please contact your first line of Hyland support.