Cribl Outage History
Uptime record, past incidents, and downtime history for Cribl.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 100% | 10 | 0 |
| March 2026 | 93.5% | 31 | 2 |
| February 2026 | 100% | 28 | 0 |
| January 2026 | 100% | 1 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 70 Days)
Jan 31
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
March 2026
Increase in errors in code function following 4.17.0 release
Started: Mar 11, 7:48 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 12, 4:47 AM
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.
Mar 12, 4:46 AM
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.
Mar 11, 9:33 PM
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.
Mar 11, 8:56 PM
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.
Mar 11, 8:38 PM
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.
Mar 11, 8:01 PM
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.
Mar 11, 7:49 PM
investigating
We are currently investigating this issue.
Mar 11, 7:48 PM