Hyland incident

Increased error rates have been identified

Minor Resolved View vendor source →

Hyland experienced a minor incident on March 13, 2025 affecting Kansas City/AWS East, USA (ARSL), lasting 16h 15m. The incident has been resolved; the full update timeline is below.

Started
Mar 13, 2025, 07:15 PM UTC
Resolved
Mar 14, 2025, 11:31 AM UTC
Duration
16h 15m
Detected by Pingoru
Mar 13, 2025, 07:15 PM UTC

Affected components

Kansas City/AWS East, USA (ARSL)

Update timeline

  1. investigating Mar 13, 2025, 07:15 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 Mar 13, 2025, 07:46 PM UTC

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

  3. monitoring Mar 13, 2025, 09:07 PM UTC

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

  4. resolved Mar 14, 2025, 11:31 AM UTC

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