# Cribl: Major incident: High CPU utilization on Lakehouses

**Summary:** _summary pending_
- Kind: Major incident · Label: major (vendor)
- Changed: 2025-06-23 18:24 UTC · Detected: 2026-10-19 18:33 UTC
- [Source: https://stspg.io/7ss7blnbt3v1](https://stspg.io/7ss7blnbt3v1)
- [Company: Cribl](https://rewindex.com/company/cribl.md)
- Versions: before (none: first archived) → after incident\_version:731/xrfbrz4rzfp2@6fc84ec8f89b
- Change 1 of 1 for this incident

Incident page (full timeline): [High CPU utilization on Lakehouses](https://rewindex.com/company/cribl/incidents/xrfbrz4rzfp2.md)
## What changed

**1. Added: Title**

```diff
+ High CPU utilization on Lakehouses
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2025-06-23 18:24 UTC
```

**5. Added: Resolved time**

```diff
+ 2025-06-26 18:29 UTC
```

**6. Added: Affected components**

```diff
+ Cribl Lake, Global - Cribl Lake
```

**7. Added: Update** (investigating) · 2025-06-23 18:24 UTC

```diff
+ We are currently investigating this issue.
```

**8. Added: Update** (investigating) · 2025-06-23 18:26 UTC

```diff
+ We're currently investigating an issue with high CPU utilization on small Lakehouses. No customer action required at this time. If you are impacted, you will see delayed or failing searches to Lakehouse.
```

**9. Added: Update** (investigating) · 2025-06-23 19:35 UTC

```diff
+ Update: We have restarted the impacted Lakehouses, which is allowing them to slowly return to a normal state. There is still no Customer action required at this time. Investigating: We are still in the process of investigating a long-term resolution, and the incident is still active.
```

**10. Added: Update** (identified) · 2025-06-23 20:46 UTC

```diff
+ The issue has been identified and a fix is being implemented.
```

**11. Added: Update** (monitoring) · 2025-06-23 20:48 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**12. Added: Update** (monitoring) · 2025-06-24 16:01 UTC

```diff
+ Update: The impacted tenants have been restarted, and are being actively monitored for the impact-thresholds. We will proactively intervene if necessary, but tenants should be performing as expected. Investigating: Engineering has identified the trigger and is finalizing long-term remediation plans.
```

**13. Added: Update** (identified) · 2025-06-26 12:56 UTC

```diff
+ The issue has been identified and a fix is being implemented.
```

**14. Added: Update** (identified) · 2025-06-26 18:08 UTC

```diff
+ Cribl will be performing an Emergency Maintenance at 2pm ET and 4pm ET in order to remediate this Incident. During this time, Customers should expect small windows of slow searches from Cribl Search to Lakehouse datasets during this time. If your Lakehouse does not perform as expected after this time, please contact Cribl Support for assistance.
```

**15. Added: Update** (monitoring) · 2025-06-26 18:29 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**16. Added: Update** (resolved) · 2025-06-26 18:29 UTC

```diff
+ This incident has been resolved.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2025-06-23 18:24 UTC | Major incident: High CPU utilization on Lakehouses (this change) | major |

All Cribl changes: [timeline](https://rewindex.com/company/cribl/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i18e3e53750f3bd · Markdown: https://rewindex.com/change/i18e3e53750f3bd.md · JSON: https://rewindex.com/api/v1/changes/i18e3e53750f3bd · Generated 2026-10-20T00:01:10.508Z