Some systems are experiencing issues

About This Site

This is the official status page for TraceHold. We publish real-time availability of our services (console, API, DLP engine, and inference nodes) and the history of incidents and maintenance. If you notice a problem not reflected here, email us at support@tracehold.com.

Past Incidents

06 Jul 2026 · Madrid time (CET/CEST)

LLM Node Outage in LLM Node
· 3 months ago

We are investigating an availability issue in LLM Node. The service is not responding correctly and our monitoring system has started automatic diagnosis and remediation. We will post updates here.

Technical probe detail: No response (timed out)

  • Automated remediation executed (result: NOT RESOLVED). Full diagnostic detail has been sent to the on-call team.

    · 3 months ago

    • 05 Jul 2026 · Madrid time (CET/CEST)

    Mail Service Outage in Mail Service
    · 3 months ago

    Mail Service is operational again. The service has recovered and automated checks are passing.

    Total outage duration: 6 min.

  • Mail Service is operational again. The service has recovered and automated checks are passing.

    Total outage duration: 6 min.

    · 3 months ago

  • Investigating: automated monitoring detected a mail service disruption and an automatic recovery check was run. Escalated for manual review.

    · 3 months ago
    • Public Website Outage in Public Website
    · 3 months ago

    Public Website is operational again. The service has recovered and automated checks are passing.

    Total outage duration: 6 min.

  • Public Website is operational again. The service has recovered and automated checks are passing.

    Total outage duration: 6 min.

    · 3 months ago

  • Investigating: automated monitoring detected the outage and an automatic recovery check was run. Escalated for manual review.

    · 3 months ago
    • LLM Node Elevated latency on the LLM Node
    · 3 months ago

    We are investigating an increase in latency on the LLM Node.

  • Resolved. LLM Node operational. Duration: 12 min.

    · 3 months ago

  • Reassociation completed. Monitoring latency.

    · 3 months ago

  • Cause identified: the floating IP stopped routing. Applying automatic reassociation.

    · 3 months ago
    • API Backend Backend outage due to full disk
    · 3 months ago

    The production backend lost its database (PostgreSQL went into PANIC due to the disk being at 100%). Cause: release-artifact backups (~7 GB every 6 h) were not being pruned and filled the disk. Resolution: freed up space (100%->15%), restarted PostgreSQL and the backend, and fixed the backup rotation so this cannot happen again. Service restored.

    04 Jul 2026 · Madrid time (CET/CEST)

    No incidents reported

    03 Jul 2026 · Madrid time (CET/CEST)

    No incidents reported

    02 Jul 2026 · Madrid time (CET/CEST)

    No incidents reported

    01 Jul 2026 · Madrid time (CET/CEST)

    No incidents reported

    30 Jun 2026 · Madrid time (CET/CEST)

    No incidents reported

    English / Español

    Website  ·  Support  ·  © 2026 TraceHold BV