Hypatos Outage History

Hypatos is up right now

Hypatos had 5 outages in the last 2 years totaling 21h 37m of downtime — averaging 0.2 incidents per month.

There were 5 Hypatos outages since July 22, 2024 totaling 21h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hypatos.ai

Notice June 1, 2026

**Investigating — Insights delays**

Detected by Pingoru
Jun 01, 2026, 01:09 PM UTC
Resolved
Jun 01, 2026, 04:30 PM UTC
Duration
3h 21m
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved Jun 02, 2026, 08:32 AM UTC

    As per our provider: Issue is resolved.

Read the full incident report →

Notice March 16, 2026

Performance degradation in EU Cluster

Detected by Pingoru
Mar 16, 2026, 01:59 PM UTC
Resolved
Mar 16, 2026, 05:04 PM UTC
Duration
3h 5m
Timeline · 3 updates
  1. 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.

  2. identified Mar 16, 2026, 01:59 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Mar 16, 2026, 05:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 16, 2025

Performance Degradation on Hy Studio

Detected by Pingoru
Jul 16, 2025, 08:35 AM UTC
Resolved
Jul 16, 2025, 12:54 PM UTC
Duration
4h 18m
Timeline · 4 updates
  1. 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.

  2. investigating Jul 16, 2025, 09:47 AM UTC

    We are still investigating the issue.

  3. monitoring Jul 16, 2025, 10:45 AM UTC

    A fix was implemented and we're now monitoring the performance.

  4. resolved Jul 16, 2025, 12:54 PM UTC

    This incident has been solved.

Read the full incident report →

Notice February 7, 2025

Performance Degradation in EU Cluster

Detected by Pingoru
Feb 07, 2025, 02:50 PM UTC
Resolved
Feb 07, 2025, 09:46 PM UTC
Duration
6h 55m
Timeline · 3 updates
  1. 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.

  2. monitoring Feb 07, 2025, 04:30 PM UTC

    A Fix was implemented and we're monitoring it's status.

  3. resolved Feb 07, 2025, 09:46 PM UTC

    This incident is now resolved. We did not see any more issues during the monitoring phase.

Read the full incident report →

Major July 22, 2024

Service Disruption - Extraction Processing Delays

Detected by Pingoru
Jul 22, 2024, 01:57 PM UTC
Resolved
Jul 22, 2024, 05:52 PM UTC
Duration
3h 55m
Timeline · 5 updates
  1. investigating Jul 22, 2024, 01:57 PM UTC

    We are currently experiencing delays in our Extraction processing system. This may result in slower document processing times than usual. Our team is actively investigating the issue and working towards a resolution. We apologize for any inconvenience caused and will provide updates as soon as possible.

  2. investigating Jul 22, 2024, 01:57 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 22, 2024, 02:34 PM UTC

    The issue was identified and we're now in the process of implementing a fix.

  4. monitoring Jul 22, 2024, 02:47 PM UTC

    Right now the fix is fully implemented and we're monitoring the system. The documents are now flowing.

  5. resolved Jul 22, 2024, 05:52 PM UTC

    The incident is now solved after confirmation. Please let us know if you feel any disruption.

Read the full incident report →