Live / Red Hat / Incident
Red Hat: Red Hat Lightspeed Compliance Degraded Performance
Red Hat · redhat.comMinor incidentResolved2026-11-02 10:33 UTC
Public — what happened
Summary
Red Hat reported degraded performance in the compliance component of Red Hat Lightspeed, where new inventory events were slow to be processed and could wait in a queue for a while. The company said a code change caused the problem, which it dated to 2026-10-28 02:00 UTC, and that it deployed a first set of fixes after identifying the problem areas. By 2026-10-30 Red Hat said the processing delay had dropped from several hours to 5-20 minutes while work on further improvements continued, and the incident was marked resolved on 2026-11-02.
Affected
Red Hat Lightspeed - Compliance
Timeline
- Started — 2026-10-29 10:15 UTC
- Identified — 2026-10-29 10:15 UTC (2 updates)
- Resolved — 2026-11-02 10:33 UTC · 4 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Red Hat against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Red Hat: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Red Hat report →
More from Red Hat
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.