Is Cribl down?
Last checked 2m agoNo incidents right now.
Cribl is operational right now. Last checked 2m ago; the most recent incident resolved 24d 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 1 incident in the last 90 days (99.84% uptime). Get email, Slack, Discord, or webhook alerts the moment Cribl reports a new incident — free for 5 monitors, no credit card.
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.
-
- Started Aug 20, 2026, 06:13 PM UTC · Resolved Aug 21, 2026, 03:30 PM UTC · 21h 17m