Cribl Outage History

Cribl is up right now

Cribl had 9 outages in the last 2 years totaling 191h 53m of downtime — averaging 0.4 incidents per month.

There were 9 Cribl outages since June 23, 2025 totaling 191h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cribl.cloud

Major April 22, 2026

Volume drop in Insights Metrics post 4.17.1 Upgrade

Detected by Pingoru
Apr 22, 2026, 10:18 PM UTC
Resolved
Apr 23, 2026, 06:59 PM UTC
Duration
20h 40m
Timeline · 6 updates
  1. investigating Apr 22, 2026, 10:18 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 22, 2026, 10:19 PM UTC

    We are currently investigating an issue where some metrics in Insights are appearing incomplete. Customer data remains secure and unaffected. We are working toward a resolution and will provide the next update at the top of the hour.

  3. investigating Apr 22, 2026, 10:19 PM UTC

    We are currently investigating an issue where some metrics in Insights are appearing incomplete. Customer data remains secure and unaffected. We are working toward a resolution and will provide the next update at the top of the hour.

  4. monitoring Apr 22, 2026, 10:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Apr 22, 2026, 10:42 PM UTC

    A fix has been implemented. Metrics are currently backfilling, and we anticipate all data will be available by the top of the hour. No further impact is expected.

  6. resolved Apr 23, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Some Cribl Cloud workspaces have data plane workers with incorrect product versions

Detected by Pingoru
Apr 22, 2026, 01:51 PM UTC
Resolved
Apr 22, 2026, 03:03 PM UTC
Duration
1h 12m
Timeline · 5 updates
  1. investigating Apr 22, 2026, 01:51 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 22, 2026, 01:51 PM UTC

    Some workspaces are experiencing data plane workers with incorrect product versions and minimal impact to the data plane. The team is currently investigating and triaging the issue.

  3. identified Apr 22, 2026, 01:52 PM UTC

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

  4. monitoring Apr 22, 2026, 02:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 22, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 16, 2025

Cribl.Cloud login issue

Detected by Pingoru
Nov 16, 2025, 08:21 PM UTC
Resolved
Nov 16, 2025, 08:59 PM UTC
Duration
37m
Timeline · 3 updates
  1. identified Nov 16, 2025, 08:21 PM UTC

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

  2. identified Nov 16, 2025, 08:22 PM UTC

    We have identified a potential service degradation to Cribl.Cloud logins; caused by an issue identified with our authentication provider. We will update this status page regularly.

  3. resolved Nov 16, 2025, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 11, 2025

A limited population of Cribl Cloud organizations are experiencing disruptions to the control and data plane

Detected by Pingoru
Aug 11, 2025, 03:52 PM UTC
Resolved
Aug 11, 2025, 04:31 PM UTC
Duration
39m
Timeline · 4 updates
  1. identified Aug 11, 2025, 03:52 PM UTC

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

  2. identified Aug 11, 2025, 03:52 PM UTC

    A limited population of Cribl Cloud organizations are experiencing disruptions to their control and data planes. Some control plane services (such as Cribl Search) may be in a degraded state and certain data flows may be impacted. We are actively investigating and remediating the issue to impacted customers. Cribl support will proactively reach out to impacted customers. Please be on the lookout for an email to the owners of the organization.

  3. monitoring Aug 11, 2025, 04:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 11, 2025, 04:31 PM UTC

    This incident has been resolved.

Read the full incident report →