Rewindex

CompaniesCriblIncidents

Cribl: Searches terminated prematurely

MajorStatus: resolvedStarted Resolved (26 h)8 updatesstspg.io (opens in new tab)

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. identified

    Cribl Status Page Update STATUS: INVESTIGATING Cribl.Cloud Search issues Status: Our engineering team is investigating an issue where long running searches are being terminated earlier than expected. Customer Impact: Any long running searches, more than 9 mins, are being terminated. This incident affects Cribl.Cloud Search.

  4. identified

    Status: Our engineering team has identified an issue that is causing long running searches to be terminated earlier than expected. We're working on a fix and plan to have it available tomorrow. Customer Impact: Any searches running longer than 9 mins are being terminated. This incident affects Cribl.Cloud Search.

  5. identified

    Incident Status: Identified Status: Our engineering team has identified an issue that is causing long running searches to be terminated earlier than expected. We're working on a fix and plan to have it available today. Customer Impact: Any searches running longer than 9 mins are being terminated. This incident affects Cribl.Cloud Search.

  6. identified

    Incident Status: Identified Status: Our engineering team continues to work on a fix and plan to have it available today. Customer Impact: Any searches running longer than 9 mins are being terminated. This incident affects Cribl.Cloud Search.

  7. identified

    Incident Status: Identified Status: Our engineering team has completed a fix and it's in the process of being deployed. Customer Impact: Any searches running longer than 9 mins are being terminated. This incident affects Cribl.Cloud Search.

  8. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cribl profileRecent Cribl incidentsMarkdownJSON