Live / Red Hat / Incident
Red Hat: Registry Proxy Pull Performance is Degraded
Red Hat · redhat.comMajor incidentResolved2026-10-22 01:18 UTC
Public — what happened
Summary
Red Hat reported a major incident in which downloading container images from its registry proxy was slower than normal. The company said the problem began at 23:36 UTC on 2026-10-21 and that it had been linked to a separate service the registry relies on. Red Hat said it was waiting on the team responsible for that service to investigate and decide next steps. The incident was marked resolved at 01:18 UTC on 2026-10-22.
Timeline
- Started — 2026-10-21 23:36 UTC
- Identified — 2026-10-21 23:36 UTC
- Investigating — 2026-10-21 23:41 UTC
- Resolved — 2026-10-22 01:18 UTC · 1h 42m 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 44, 2026, our weekly internet health report.