Cribl Outage History

Cribl is up right now

Cribl had 19 outages in the last 2 years totaling 304h 56m of downtime — averaging 0.8 incidents per month.

There were 19 Cribl outages since November 6, 2024 totaling 304h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cribl.cloud

Major September 18, 2026

Cribl Insights showing incomplete data

Detected by Pingoru
Sep 18, 2026, 07:46 PM UTC
Resolved
Sep 18, 2026, 09:52 PM UTC
Duration
2h 6m
Timeline · 4 updates
  1. investigating Sep 18, 2026, 07:46 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 18, 2026, 08:05 PM UTC

    We are actively investigating an issue causing Insights to display We are actively investigating an issue causing Insights to display incomplete metric reports. Our team is working to isolate the root cause. We will provide our next update at the top of the hour or as soon as we have more details.

  3. investigating Sep 18, 2026, 09:08 PM UTC

    We are actively investigating an issue causing Insights to display incomplete metric reports. Our team is working to isolate the root cause. We will provide our next update at the top of the hour or as soon as we have more details.

  4. resolved Sep 18, 2026, 09:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2026

OAuth secret expressions fail to resolve during authentication after 4.20.0 upgrade

Detected by Pingoru
Sep 16, 2026, 02:52 PM UTC
Resolved
Sep 18, 2026, 07:41 PM UTC
Duration
2d 4h
Timeline · 7 updates
  1. investigating Sep 16, 2026, 02:52 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 16, 2026, 03:33 PM UTC

    Investigating: We are continuing to investigate an issue that may prevent OAuth secret expressions on Microsoft Sentinel destinations from resolving during authentication following the 4.20.0 upgrade.

  3. investigating Sep 16, 2026, 04:34 PM UTC

    Update: We are continuing our investigation regarding this issue.

  4. identified Sep 16, 2026, 05:44 PM UTC

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

  5. monitoring Sep 16, 2026, 05:57 PM UTC

    We have published a known issue with a workaround for this issue. See https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304

  6. monitoring Sep 16, 2026, 06:23 PM UTC

    Mitigated: We have identified the issue affecting OAuth secret expressions following the 4.20.0 upgrade and published a Known Issue with a workaround. Customers experiencing authentication failures can follow the documented workaround. Known Issue can be found here: https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304

  7. resolved Sep 18, 2026, 07:41 PM UTC

    This incident has been resolved.

Read the full incident report →

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 →

Major April 14, 2025

Cribl.cloud Authentication Slowness

Detected by Pingoru
Apr 14, 2025, 10:54 PM UTC
Resolved
Apr 15, 2025, 12:29 AM UTC
Duration
1h 34m
Affected: Login & Registration
Timeline · 3 updates
  1. identified Apr 14, 2025, 10:54 PM UTC

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

  2. monitoring Apr 14, 2025, 11:09 PM UTC

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

  3. resolved Apr 15, 2025, 12:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 20, 2025

Some Cribl Cloud Control Plane features are degraded

Detected by Pingoru
Feb 20, 2025, 06:25 PM UTC
Resolved
Feb 21, 2025, 10:32 PM UTC
Duration
1d 4h
Timeline · 6 updates
  1. identified Feb 20, 2025, 06:25 PM UTC

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

  2. identified Feb 20, 2025, 06:26 PM UTC

    We're currently experiencing issues with Cribl Cloud infrastructure management functions. Users may encounter problems when attempting to create/update Worker Groups & Workspaces. Important: There is no impact on data processing. Our team is actively investigating and working to resolve this issue. We'll provide updates as soon as we have more information.

  3. monitoring Feb 21, 2025, 01:39 AM UTC

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

  4. identified Feb 21, 2025, 10:26 AM UTC

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

  5. identified Feb 21, 2025, 08:08 PM UTC

    We have identified a issue with control plane in Cribl.Cloud and will be applying a hotfix at 4pm ET today, with no interruption. There is no impact to data processing or regular use of Cribl.Cloud. Users may encounter trouble with the following: - Provisioning new worker groups within an existing workspace - modify existing worker groups within an existing workspace

  6. resolved Feb 21, 2025, 10:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 29, 2025

Cribl Cloud Emergency Worker Maintenance

Detected by Pingoru
Jan 29, 2025, 06:41 PM UTC
Resolved
Jan 29, 2025, 08:05 PM UTC
Duration
1h 23m
Timeline · 3 updates
  1. identified Jan 29, 2025, 06:41 PM UTC

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

  2. identified Jan 29, 2025, 06:41 PM UTC

    We are performing urgent maintenance on Cribl Cloud to replace instances of affected worker nodes. Data processing will continue uninterrupted during remediation actions.

  3. resolved Jan 29, 2025, 08:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 8, 2025

Cloud portal not accessible

Detected by Pingoru
Jan 08, 2025, 03:14 PM UTC
Resolved
Jan 08, 2025, 03:25 PM UTC
Duration
11m
Timeline · 5 updates
  1. identified Jan 08, 2025, 03:14 PM UTC

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

  2. identified Jan 08, 2025, 03:15 PM UTC

    This issue has been mitigated. Customers should be able to access the Cloud Portal now.

  3. monitoring Jan 08, 2025, 03:15 PM UTC

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

  4. monitoring Jan 08, 2025, 03:17 PM UTC

    This issue has been mitigated. Customers should be able to access the Cloud Portal now.

  5. resolved Jan 08, 2025, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 6, 2024

Multiple organizations did not upgrade during 4.9.1 cloud release

Detected by Pingoru
Nov 06, 2024, 02:49 PM UTC
Resolved
Nov 06, 2024, 05:13 PM UTC
Duration
2h 23m
Timeline · 6 updates
  1. investigating Nov 06, 2024, 02:49 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 06, 2024, 02:52 PM UTC

    We have identified some Cribl Cloud Organizations have not yet upgraded to version 4.9.1 and are investigating the root cause further. Some users may see version 4.9.0 still active, and may also experience some UI refreshes as we work to resolve the version upgrade. Please contact '[email protected]' if you have any questions or concerns.

  3. investigating Nov 06, 2024, 03:48 PM UTC

    Cribl Cloud Engineering are diligently working to upgrade the remaining Cloud Organizations to version 4.9.1. We will continue to provide updates here, but please feel free to contact '[email protected]' if you have any immediate questions or concerns.

  4. investigating Nov 06, 2024, 04:39 PM UTC

    We have identified the issue affecting some Cribl Cloud Organizations from upgrading to version 4.9.1. We are now addressing the last few Organizations and will post a progress update shortly.

  5. investigating Nov 06, 2024, 05:10 PM UTC

    Cribl Engineering have successfully upgraded the affected Organizations to version 4.9.1.

  6. resolved Nov 06, 2024, 05:13 PM UTC

    This incident has been resolved.

Read the full incident report →