Cribl incident
Increase in errors in code function following 4.17.0 release
Cribl experienced a major incident on March 11, 2026, lasting 22h 50m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Mar 11, 2026, 07:48 PM UTC
We are currently investigating this issue.
- investigating Mar 11, 2026, 07:49 PM UTC
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 Mar 11, 2026, 08:01 PM UTC
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 Mar 11, 2026, 08:38 PM UTC
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 Mar 11, 2026, 08:56 PM UTC
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 Mar 11, 2026, 09:33 PM UTC
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 Mar 12, 2026, 04:46 AM UTC
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.
- monitoring Mar 12, 2026, 04:47 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 12, 2026, 06:39 PM UTC
This incident has been resolved.