All Systems Operational

Ashburn, USA (IAD) ? Operational
Queretaro, Mexico (QRO) ? Operational
Sydney, Australia (SYD) ? Operational
AWS Frankfurt (AMS) ? Operational
Melbourne, Australia (MEL) ? Operational
Boyers, USA (PIT) ? Operational
London, UK (LHR) ? Operational
Auckland, New Zealand (AKL) ? Operational
Toronto, Canada (D01) ? Operational
Kansas City/AWS East, USA (ARSL) ? Operational
AWS Northern Virginia (AWVA) ? Operational
AWS Ireland (AWIE) ? Operational
AWS Tokyo (HND) ? Operational
Sydney, Australia (BWU) ? Operational
London Gatwick, UK (LGW) ? Operational
Portland, USA (PDX) ? Operational
Arlington, USA (DCA) Operational
Sao Paulo, Brazil (GRU) Operational
AWS Melbourne, Australia (AVV) ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Apr 26, 2025

No incidents reported today.

Apr 25, 2025
( Status: Resolved ) Increased error rates have been identified in the PIT data center
Resolved - This incident has been resolved. If you continue to experience issues please contact your first line of support.
Apr 25, 12:00 UTC
Update - We are continuing to monitor the result of the applied fixes. We will provide further updates tomorrow, April 25th, at 9:00 AM Eastern Time.
Apr 25, 02:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results. If issues persist, application pools or services may need to be restarted, and document/process locks may need to be cleared.
Apr 25, 01:17 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 25, 00:19 UTC
Investigating - Hyland is aware of increased error rates in the PIT data center. Hyland is engaged and investigating this issue with the highest priority. Additional details will be provided as they become available.
Apr 24, 23:49 UTC
Apr 24, 2025
Increased error rates have been resolved
Resolved - Hyland has remediated the issue. If you continue to have any issues please contact your first line of Hyland support.
Apr 24, 13:00 UTC
Monitoring - Remediation for Production environments is complete, and we are now transitioning to the monitoring stage. We are also making continued progress on addressing the issue in UT environments. We will provide further updates tomorrow, April 24th, at 9:00 AM Eastern Time.
Apr 23, 20:50 UTC
Update - We are actively working on a fix for this issue. Some customer systems have already recovered, while others are still impacted. Our team remains fully engaged and focused on ensuring that all customer systems are fully restored
Apr 23, 19:42 UTC
Update - We are actively working on a fix for this issue. Some customer systems have already recovered, while others are still impacted. Our team remains fully engaged and focused on ensuring that all customer systems are fully restored
Apr 23, 18:29 UTC
Update - We are continuing to work on a fix for this issue.
Apr 23, 17:27 UTC
Update - We are continuing to work on a fix for this issue.
Apr 23, 16:21 UTC
Update - We are continuing to work on a fix for this issue.
Apr 23, 15:17 UTC
Update - We are continuing to work on a fix for this issue.
Apr 23, 14:11 UTC
Update - We are continuing to work on a fix for this issue.
Apr 23, 13:08 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 23, 12:10 UTC
Update - We are continuing to investigate this issue.
Apr 23, 11:09 UTC
Update - We are continuing to investigate this issue.
Apr 23, 10:11 UTC
Investigating - 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.
Apr 23, 09:10 UTC
Apr 23, 2025
Increased error rates have been identified
Resolved - This incident has been resolved.
Apr 23, 15:24 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 23, 15:17 UTC
Update - We are continuing to investigate this issue.
Apr 23, 14:31 UTC
Investigating - 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.
Apr 23, 13:42 UTC
Apr 22, 2025

No incidents reported.

Apr 21, 2025
Increased error rates have been identified
Resolved - Hyland has remediated the issue. If you continue to have any issues please contact your first line of Hyland support.
Apr 21, 15:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 21, 15:18 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 21, 15:10 UTC
Investigating - 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.
Apr 21, 14:32 UTC
Apr 20, 2025
Increased error rates have been identified
Resolved - This incident has been resolved.
Apr 20, 16:24 UTC
Monitoring - Hyland believes the issue is resolved. We are still actively monitoring.
Apr 20, 16:13 UTC
Identified - 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.
Apr 20, 15:40 UTC
Update - We are continuing to investigate this issue.
Apr 20, 15:01 UTC
Update - We are continuing to investigate this issue.
Apr 20, 14:11 UTC
Update - We are continuing to investigate this issue.
Apr 20, 12:58 UTC
Update - We are continuing to investigate this issue.
Apr 20, 11:53 UTC
Investigating - 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.
Apr 20, 10:54 UTC
Apr 19, 2025
Increased error rates have been identified
Resolved - Hyland has remediated the issue. If you continue to have any issues please contact your first line of Hyland support.
Apr 19, 19:52 UTC
Investigating - 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.
Apr 19, 18:56 UTC
Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025

No incidents reported.

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage