Cribl Outage History
Daily status observations, past incidents, and reported issue history for Cribl.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 100% | 25 | 0 |
| July 2026 | 100% | 31 | 0 |
| June 2026 | 100% | 30 | 0 |
| May 2026 | 100% | 5 | 0 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
OAuth secrets containing C.* expressions fail to resolve during authentication
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
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 o...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: Will occur at th...
identified
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 support@cribl.io.
Next Update: In 1 hour or as soon as new information becomes available.
identified
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 support@cribl.io.
Next Update: In 1 hour or as soon as new information becomes available.
identified
The issue has been identified and a fix is being implemented.
April 2026
Volume drop in Insights Metrics post 4.17.1 Upgrade
Started:
monitoring
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.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
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.
investigating
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.
investigating
We are currently investigating this issue.
Some Cribl Cloud workspaces have data plane workers with incorrect product versions
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
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.
investigating
We are currently investigating this issue.
March 2026
Increase in errors in code function following 4.17.0 release
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
We are currently investigating this issue.