(Status: Monitoring) Increased error rates have been identified in AKL Datacenter
Monitoring - Performance improvements have been observed, and system stability continues to trend in a positive direction. Teams remain actively engaged in monitoring the environment and will share additional updates as more information becomes available.
May 15, 2026 - 13:58 UTC
Identified - The datacenter vendor has identified the issue and is actively working on a resolution. Additional details will be shared as they become available.
May 15, 2026 - 13:42 UTC
(Status: Identified) Increased error rates have been identified - IAD
Update - Hyland has identified a resolution, and are currently in the planning stages with a target implementation date of 5/24. The next update will be provided by May 20, 2026 at 5:00 PM ET, or sooner if additional information becomes available.
May 14, 2026 - 19:43 UTC
Identified - Hyland has identified the underlying issue and is actively collaborating with its vendor to implement a resolution. The next update will be provided by May 14, 2026 at 5:00 PM ET, or sooner if additional information becomes available.
May 13, 2026 - 19:51 UTC
Update - Hyland has identified the underlying issue and is actively collaborating with its vendor to implement a resolution. The next update will be provided by May 14, 2026 at 5:00 PM ET, or sooner if additional information becomes available.
May 13, 2026 - 19:50 UTC
Update - Investigation continues in coordination with the vendor, and improvements to overall solution stability have been observed. The next update will be provided by May 13, 2026 at 5:00 PM ET, or sooner if additional information becomes available.
May 12, 2026 - 19:53 UTC
Update - Hyland has escalated with the vendor to investigate the issue with the highest priority.  The next update will be shared by May 12, 2026 at 5:00pm ET.
May 12, 2026 - 18:54 UTC
Update - Hyland is engaging the vendor to investigate the issue. Further updates will be provided as additional information becomes available. The next update will be shared by May 12, 2026 at 3:00 PM ET.
May 12, 2026 - 17:22 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.
May 12, 2026 - 14:52 UTC
Ashburn, USA (IAD) Degraded Performance
Sydney, Australia (SYD) Operational
AWS Frankfurt (AMS/QEF) 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
Richmond, USA (RIC) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 17, 2026

No incidents reported today.

May 16, 2026

No incidents reported.

May 15, 2026
(Status: Resolved) Connectivity Issues - DCA
Resolved - System connectivity has been restored and is currently stable following the applied fix. Should you continue to experience any issues, please contact your first line of support for further assistance.
May 15, 19:37 UTC
Monitoring - A fix has been applied, and early signs of improvement are being observed. Hyland will continue to track the situation closely and provide updates as needed.
May 15, 17:27 UTC
Update - Hyland is continuing to investigate this issue on the highest priority. More information will be made available as Hyland's investigation continues.
May 15, 16:31 UTC
Investigating - Hyland is aware of ongoing issues within the DCA data center. More information will be provided when available.
May 15, 15:36 UTC
(Status: Resolved) Increased error rates have been identified - PIT
Resolved - Hyland has identified and resolved the issue. If you continue to have any issues please contact your first line of Hyland support.
May 15, 19:27 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.
May 15, 18:49 UTC
May 14, 2026

Unresolved incident: (Status: Identified) Increased error rates have been identified - IAD.

May 13, 2026
May 12, 2026
May 11, 2026
(Status: Resolved) SFTP Connection issues in QEF datacenter
Resolved - The issue with SFTP Connections in QEF datacenter has been resolved. If issues still persist, please contact your first line of support.
May 11, 21:34 UTC
Update - Hyland is continuing to work on a fix for the issue. We will provide updates as more information becomes available.
May 11, 21:20 UTC
Identified - Hyland has identified an issue impacting SFTP connectivity for a subset of customers in the QEF datacenter. The team is actively working to resolve the issue.
May 11, 19:33 UTC
(Status: Resolved) Increased error rates have been identified in IAD Datacenter.
Resolved - Hyland has fully resolved the issue affecting IAD Datacenter. Systems are operating normally, and we are no longer observing any related errors or disruptions.

We appreciate your patience and understanding while we worked to restore service. If you continue to experience any problems, please contact our first line of support.
May 11, 19:12 UTC
Update - We are continuing to monitor for any further issues.
May 11, 14:14 UTC
Update - Monitoring continues to indicate that Saturday's changes were successful, along with no reports of issues from Customers. Hyland will continue to monitor through the day and will provide an update by Monday, 5/11, 4:00 PM ET
May 11, 14:14 UTC
Monitoring - Hyland has successfully implemented a solution this evening and we will continue monitoring to ensure full resolution. An update will be provided by Monday, 5/11, 11:00 AM ET
May 10, 02:25 UTC
Update - A solution has been identified, and teams are actively working toward implementation this weekend, with long-term stability as the priority. The next update will be shared via Statuspage at 11:00 PM ET on May 9.
May 7, 17:03 UTC
Update - The issue has been identified, and teams are actively working toward a solution with long‑term stability as the priority. The next update will be provided at 4:00 PM ET on May 7.
May 7, 14:17 UTC
Update - Planned data center changes are being prepared to reinforce long‑term stability, while teams continue to work with the vendor. The next update will be provided at 10:00AM Eastern on May 7th.
May 6, 19:54 UTC
Update - Mitigating steps are currently being implemented to address this issue, with a focus on long term stability. Hyland remains actively engaged with the vendor during this process and we will share the next update at 4:00pm Eastern.
May 6, 16:27 UTC
Update - Hyland remains fully engaged with the vendor to drive remediation efforts as the highest priority. The next update will be shared by 1:00 PM ET tomorrow.
May 5, 20:50 UTC
Update - Hyland continues to work with the vendor on remediation with the highest priority. Additional updates will be shared as they become available.
May 5, 15:28 UTC
Identified - Hyland has identified the issue and is actively working with the vendor on remediation with the highest priority. Additional updates will be shared as they become available.
May 5, 13:18 UTC
Update - Hyland is still actively investigating the issue with the highest priority. Additional details will be provided as they become available.Thank you for your patience.
May 5, 07:48 UTC
Update - Hyland is still investigating the issue with the highest priority. Next update will be provided by tomorrow, May 5th, 10am Eastern.
May 4, 21:03 UTC
Update - Hyland is still investigating the issue with the highest priority. Additional details will be provided as they become available.
May 4, 20:20 UTC
Update - Hyland is still actively investigating the issue with the highest priority. Additional details will be provided as they become available.
Thank you for your patience.
May 4, 19:14 UTC
Update - Hyland is still investigating the issue with the highest priority. Additional details will be provided as they become available.
May 4, 18:02 UTC
Investigating - Hyland is aware of increased error rates in IAD Datacenter. Hyland is engaged and investigating this issue with the highest priority. Additional details will be provided as they become available.
May 4, 16:52 UTC
May 10, 2026
May 9, 2026
(Status: Resolved) Degraded Performance in DCA
Resolved - AWS has confirmed that the incident in a single Availability Zone (US‑EAST‑1) caused by a thermal event has been resolved. Hyland has validated that all of our services are fully operational.
We appreciate your patience and understanding during this event. If you continue to experience any issues, please reach out to our first line of support.
May 9, 06:36 UTC
Update - AWS has confirmed a power and thermal event impacting a single Availability Zone in US-EAST-1. Recovery is in progress with signs of improvement; some services may remain degraded. AWS expects several hours for full restoration. Hyland is actively monitoring and will provide updates as they become available.
May 8, 12:49 UTC
Monitoring - AWS has advised that a thermal event is impacting parts of us-east-1. As a result this may cause degraded performance until it is fully resolved by the vendor. We are monitoring closely at this time.
May 8, 01:29 UTC
May 8, 2026
May 7, 2026
Resolved: Intermittent solution connectivity - AKL
Resolved - The issue with intermittent connectivity has been resolved. If issues continue to be experienced, please reach out to your first line of support.
May 7, 03:41 UTC
Identified - The issue has been identified and a fix is being put in place to mitigate the connectivity errors.
May 7, 02:51 UTC
Investigating - We have received reports of intermittent connection issues in the AKL datacenter. We are currently investigating this matter.
May 7, 01:41 UTC
May 6, 2026
May 5, 2026
May 4, 2026
May 3, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage