Is Cribl down?

Last checked 2m ago
Current status
Cribl is up

No incidents right now.

Official status page: https://status.cribl.cloud · Polled every 5 minutes · 21 components tracked

Cribl is operational right now. Last checked 2m ago; the most recent incident resolved 1d ago.

Real-time Cribl status, recent outages, and incident history — pulled directly from Cribl's official status page at https://status.cribl.cloud every 5 minutes. Pingoru tracks 21 Cribl services and has captured 3 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Cribl reports a new incident — free for 5 monitors, no credit card.

Users who monitor Cribl also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Cribl uptime 99.71% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 6m
    Started Sep 18, 2026, 07:46 PM UTC · Resolved Sep 18, 2026, 09:52 PM UTC
    Timeline · 4 updates
    • investigating · Sep 18, 2026, 07:46 PM UTC

      We are currently investigating this issue.

    • 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.

    • 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.

    • resolved · Sep 18, 2026, 09:52 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 2d 4h
    Started Sep 16, 2026, 02:52 PM UTC · Resolved Sep 18, 2026, 07:41 PM UTC
    Timeline · 7 updates
    • investigating · Sep 16, 2026, 02:52 PM UTC

      We are currently investigating this issue.

    • 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.

    • investigating · Sep 16, 2026, 04:34 PM UTC

      Update: We are continuing our investigation regarding this issue.

    • identified · Sep 16, 2026, 05:44 PM UTC

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

    • 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

    • 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

    • resolved · Sep 18, 2026, 07:41 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 21h 17m
    Started Aug 20, 2026, 06:13 PM UTC · Resolved Aug 21, 2026, 03:30 PM UTC
    Timeline · 12 updates
    • identified · Aug 20, 2026, 06:13 PM UTC

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

    • identified · Aug 20, 2026, 07:12 PM UTC

      We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at [email protected]. Next Update: In 1 hour or as soon as new information becomes available.

    • identified · Aug 20, 2026, 08:01 PM UTC

      We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at [email protected]. Next Update: In 1 hour or as soon as new information becomes available.

    • identified · Aug 20, 2026, 09:01 PM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 20, 2026, 09:02 PM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 20, 2026, 10:00 PM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 20, 2026, 11:10 PM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 21, 2026, 12:00 AM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 21, 2026, 01:00 AM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

    • identified · Aug 21, 2026, 01:47 AM UTC

      We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release. A fix has been prepared and will be deployed as part of a rolling upgrade. Your organization will be picked up for upgrade on a rolling basis between 01:45 and 05:45 UTC on August 21, 2026 (9:45 PM – 1:45 AM EDT, Aug 20–21). Once the upgrade begins for your tenant, it will take approximately 20 minutes to complete. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443): https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected].

    • monitoring · Aug 21, 2026, 01:49 AM UTC

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

    • resolved · Aug 21, 2026, 03:30 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →