Alerting Delay

What to do

• Check whether your product depends on Loggly. 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 0m it lasted.

  Anything that failed between 2026-08-07 20:54 UTC and 2026-08-07 20:54 UTC may need a replay.

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

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

Updates from Loggly 1

1. resolvedAug 7, 2026, 8:54 PM UTC

   On July 12, 2026, we experienced delays in our alerting system, resulting in an interruption to alert processing for some Loggly customers. The issue was traced to a production scheduler service responsible for evaluating and scheduling alerts. Due to resource exhaustion on the host, the scheduler was unable to operate normally, preventing alert jobs from being process downstream. The team restored service by increasing the capacity of the affected host, returning resource utilization to healthy levels and allowing the scheduler to resume normal operation. Following the remediation, alert processing has since been operating normally.

   provider

Corrections

None so far.

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