Is Cribl down?
Last checked 2m agoActive incident: OAuth secret expressions fail to resolve during authenticat…
Cribl is reporting degraded performance right now (last checked 2m ago). Services are up but slower or partially failing.
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 2 incidents in the last 90 days (99.79% uptime). Get email, Slack, Discord, or webhook alerts the moment Cribl reports a new incident — free for 5 monitors, no credit card.
Active incident 1
-
Timeline · 6 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
Latest: 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 authen…
-
Recent outages & incidents
Past 90 days-
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.
-
See the full Cribl outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Cribl outage history →Or sign up free to get alerts when Cribl breaks · 10 free monitors · No credit card
- Started Sep 16, 2026, 02:52 PM UTC · ● 22h 22m
- Started Aug 20, 2026, 06:13 PM UTC · Resolved Aug 21, 2026, 03:30 PM UTC · 21h 17m