Cribl Outage History

Cribl is up right now

There were 4 Cribl outages since February 22, 2026 totaling 46h 30m 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 →

Major March 11, 2026

Increase in errors in code function following 4.17.0 release

Detected by Pingoru
Mar 11, 2026, 07:48 PM UTC
Resolved
Mar 12, 2026, 06:39 PM UTC
Duration
22h 50m
Timeline · 9 updates
  1. investigating Mar 11, 2026, 07:48 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 11, 2026, 07:49 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  3. investigating Mar 11, 2026, 08:01 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  4. investigating Mar 11, 2026, 08:38 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  5. investigating Mar 11, 2026, 08:56 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  6. investigating Mar 11, 2026, 09:33 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  7. investigating Mar 12, 2026, 04:46 AM UTC

    We have confirmed that the recent increase in Code Function errors did not impact overall data flow. We identified an issue with recursive Code Function executions temporarily blocking throughput for a small number of customers. We have worked directly with the affected users to mitigate and stabilize their pipelines, and systems are operating as expected at this time and we are contiuing to monitor all signals.

  8. monitoring Mar 12, 2026, 04:47 AM UTC

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

  9. resolved Mar 12, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 22, 2026

Cribl cloud is not accessible

Detected by Pingoru
Feb 22, 2026, 05:02 PM UTC
Resolved
Feb 22, 2026, 06:49 PM UTC
Duration
1h 47m
Timeline · 9 updates
  1. investigating Feb 22, 2026, 05:02 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 22, 2026, 05:18 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to exicute.

  3. investigating Feb 22, 2026, 05:20 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to execute.

  4. identified Feb 22, 2026, 05:28 PM UTC

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

  5. identified Feb 22, 2026, 05:32 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to execute.

  6. identified Feb 22, 2026, 05:35 PM UTC

    We are continuing to monitor the status of our Identity Provider's services.

  7. identified Feb 22, 2026, 06:02 PM UTC

    Our Identity Providers status remains unchanged. We continue to track the resolution of the ongoing incident and the restoration of services.

  8. identified Feb 22, 2026, 06:49 PM UTC

    The status of our Identity Provider has returned to 'Operational.' The incident regarding authentication is now resolved, and all systems are functioning as expected. We continue to track service health as part of our post-resolution oversight.

  9. resolved Feb 22, 2026, 06:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Cribl downtime and outages?

Pingoru polls Cribl's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cribl reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cribl alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cribl for free

5 free monitors · No credit card required