Red Hat Lightspeed Compliance Degraded Performance

What to do

• Check whether you use Red Hat Red Hat Lightspeed - Compliance. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d it lasted.

  Anything that failed between 2026-10-29 10:15 UTC and 2026-11-02 10:33 UTC may need a replay.

• Subscribe to Red Hat's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=red-hat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Red Hat 4

1. identifiedOct 29, 2026, 10:15 AM UTC

   Change in the code caused degraded performance of processing new inventory events in compliance component. Events can sit for a while in the queue. Started at 2026-10-28 02:00:00 UTC and ongoing. Problematic parts were identified, first batch of remedy was deployed and the team had identified areas to improve and is addressing them in the meantime.

   provider

2. identifiedOct 30, 2026, 10:41 AM UTC

   The lag in processing of messages is lowered from several hours to 5-20 minutes. The team is working on further improvements.

   provider

3. identifiedNov 2, 2026, 10:33 AM UTC

   The application performance is stabilized.

   provider

4. resolvedNov 2, 2026, 10:33 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.