Hypatos Outage History
Hypatos is up right nowPingoru has recorded 14 incidents for Hypatos: 6 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 3 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 25 of 744 (3%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 2 | 5 of 512 (1%) |
Incidents, newest first
Critical October 13, 2026 Service Interruption - Temporary Unavailability of Enrichment Features 36m
Started Oct 13, 2026, 09:08 AM UTC· resolved Oct 13, 2026, 09:44 AM UTC
- identified Oct 13, 2026, 09:08 AM UTC
We are currently experiencing a service interruption that affects the availability some of our Enrichment features. This means that document processing using Enrichment is temporarily unavailable. Our Engineers are on the case and we will provide updates as we work towards restoring full functionality. We appreciate your patience and will update you with further information as soon as possible. All affected documents will be reprocessed as soon as the issue is solved.
- identified Oct 13, 2026, 09:09 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 13, 2026, 09:16 AM UTC
A fix was implemented and we're now monitoring the results.
- resolved Oct 13, 2026, 09:44 AM UTC
This incident was now solved. All affected documents will be reprocessed. Thank you for you patience.
Major October 8, 2026 Incorrect document counts on tabs and increased processing latency 4h 42m
Started Oct 08, 2026, 09:19 AM UTC· resolved Oct 08, 2026, 02:01 PM UTC
- investigating Oct 08, 2026, 09:19 AM UTC
Hi, We are currently experiencing two issues affecting the platform: Incorrect document counts on tabs The document counts shown on tabs in the UI may not match the actual number of documents. When you open a tab, the number of documents listed may differ from the count displayed on it. The documents themselves are correct and no data has been lost or changed. Only the count shown on the tab may be inaccurate. Our backend team has identified the cause and is working on a fix. Increased processing latency We are observing increased latency in our AI processing system, which is leading to slower response times for document analysis and extraction. Our team is actively investigating the cause and working to restore normal performance. We appreciate your patience and will share further updates as soon as possible. Kind regards,
- identified Oct 08, 2026, 09:45 AM UTC
The issue was identified and the team is working already on the fix.
- resolved Oct 08, 2026, 02:01 PM UTC
Both issues have now been resolved. Incorrect document counts on tabs The fix has been deployed and the document counts shown on tabs now match the actual number of documents. No data was lost or changed at any point. Increased processing latency Processing times for document analysis and extraction have returned to normal. Thank you for your patience while we worked on these issues. If you notice anything unexpected, please contact our support team.
Notice August 6, 2026 Errors accessing the Workflows & Agents configuration area 1d
Started Aug 06, 2026, 10:30 AM UTC· resolved Aug 07, 2026, 11:19 AM UTC
- resolved Aug 06, 2026, 01:11 PM UTC
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.
Notice June 1, 2026 **Investigating — Insights delays** 3h 21m
Started Jun 01, 2026, 01:09 PM UTC· resolved Jun 01, 2026, 04:30 PM UTC
- investigating Jun 01, 2026, 01:09 PM UTC
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.
- monitoring Jun 01, 2026, 02:44 PM UTC
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.
- resolved Jun 02, 2026, 08:32 AM UTC
As per our provider: Issue is resolved.
Notice March 16, 2026 Performance degradation in EU Cluster 3h 5m
Started Mar 16, 2026, 01:59 PM UTC· resolved Mar 16, 2026, 05:04 PM UTC
- identified Mar 16, 2026, 01:59 PM UTC
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.
- identified Mar 16, 2026, 01:59 PM UTC
We are continuing to work on a fix for this issue.
- resolved Mar 16, 2026, 05:04 PM UTC
This incident has been resolved.
Notice July 16, 2025 Performance Degradation on Hy Studio 4h 18m
Started Jul 16, 2025, 08:35 AM UTC· resolved Jul 16, 2025, 12:54 PM UTC
- investigating Jul 16, 2025, 08:35 AM UTC
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.
- investigating Jul 16, 2025, 09:47 AM UTC
We are still investigating the issue.
- monitoring Jul 16, 2025, 10:45 AM UTC
A fix was implemented and we're now monitoring the performance.
- resolved Jul 16, 2025, 12:54 PM UTC
This incident has been solved.
Notice February 7, 2025 Performance Degradation in EU Cluster 6h 55m
Started Feb 07, 2025, 02:50 PM UTC· resolved Feb 07, 2025, 09:46 PM UTC
- investigating Feb 07, 2025, 02:50 PM UTC
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.
- monitoring Feb 07, 2025, 04:30 PM UTC
A Fix was implemented and we're monitoring it's status.
- resolved Feb 07, 2025, 09:46 PM UTC
This incident is now resolved. We did not see any more issues during the monitoring phase.