Hypatos had 5 outages in the last 2 years totaling 17h 41m of downtime — averaging 0.2 incidents per month.
There were 5 Hypatos outages since February 7, 2025 totaling 17h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Resolved — [12:19 CET] Between [11:45] and [12:19 CET], some users encountered errors when opening the setup area for Workflows and Agents. The cause was an unresponsive system, and a fix has been applied. Existing workflows and agents continued running, and no data was affected. The setup area is now operating as expected. We apologize for the disruption.
We're monitoring an upstream incident with one of our infrastructure providers (ClickHouse - https://status.clickhouse.com/) that may affect parts of our Insights system. The provider has identified the root cause and is working on a resolution. We'll post updates here as we learn more. No action is needed on your end.
The provider informed that the root cause was identified and issue was fixed. Connectivity issues should not happen again. We're confirming it with them.
As per our provider: Issue is resolved.
We are currently experiencing poor performance during document upload and processing on our EU Cluster. Our Customer Care and Engineering teams are actively working on it. Sorry for the inconvenience created.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently experiencing poor performance on Hy Studio EU Cluster. Please note that this is only affecting the User Interface and not the document processing system in the backend. Our Customer Care and Engineering teams are actively working on it. Sorry for the inconvenience created. We will come back with an update at 11h30 CET.
We are still investigating the issue.
A fix was implemented and we're now monitoring the performance.
This incident has been solved.
We are currently experiencing poor performance during document upload and processing on our EU Cluster. Our Customer Care and Engineering teams are actively working on it. Sorry for the inconvenience created. We will come back with an update at 16h00 CET.
A Fix was implemented and we're monitoring it's status.
This incident is now resolved. We did not see any more issues during the monitoring phase.