Investigation
On February 17, 2026, at 11:26 PM CET, we detected an issue where the Library Insights feature in the Hive environment began timing out. The issue affected administrators with space owner permissions who were accessing analytics data within Library Insights.
The engineering team initiated the Investigation phase on February 18, 2026, at 12:12 PM CET. Early analysis identified that SQL queries against the database were experiencing elevated CPU usage, reaching sustained peaks that resulted in query timeouts. Further review showed that specific filter-related queries (such as application, countries, and departments) were contributing to the increased database load.
The team focused on stabilizing database performance while continuing a deeper analysis of the query patterns contributing to the issue.
Mitigation
As an immediate mitigation step, the engineering team increased the compute capacity of the database.
The initial capacity increase did not fully alleviate the performance constraints, and additional scaling actions were taken. By 1:26 PM CET on February 18, 2026, after the additional scaling adjustments were completed, database CPU utilization stabilized and query timeouts ceased.
The team continued monitoring the system closely to ensure sustained stability.
Resolution
By 1:26 PM CET on February 18, 2026, the increased database capacity successfully stabilized the environment and restored consistent functionality to the Library Insights feature.
No further disruptions were reported after the scaling adjustments were completed. Performance levels returned to expected operational thresholds following continued monitoring and system stabilization.
Post-Incident Actions
Following the incident, we initiated a deeper review of the query patterns used in Library Insights.
As part of our follow-up actions:
These improvements are intended to strengthen performance resilience as data volumes continue to grow.
Impact and Scope
The incident impacted the Library Insights feature within the Hive environment.
Scope of impact:
The disruption was limited in scope and did not impact end users outside of the administrative analytics functionality.
We sincerely apologize for the disruption caused by this issue. Ensuring reliable performance and a seamless experience for administrators and end users alike remains our highest priority. We are implementing the improvements outlined above to further strengthen system stability and prevent similar occurrences in the future.