Delayed data ingestion

What to do

• Check whether you use Loggly in us. 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-09-04 20:37 UTC and 2026-09-03 22:52 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. resolvedSep 3, 2026, 10:52 PM UTC

   Customer Impact A small number of customers experienced delayed data ingestion and alerts that were not processed in real time. No customer data was lost. Incident Update On September 3, 2026, at 10:52 PM UTC, an infrastructure component became unavailable, resulting in a processing backlog and delays in alert handling. A separate alert-grouping issue delayed notification to the on-call team, extending the time to response. In addition, an issue with our in-app messaging prevented us from providing timely customer notifications within the app. The incident was fully resolved after 18 hours and 49 minutes. Data processing and alert handling have returned to normal, and no customer data was lost. We are reviewing our alert-grouping behavior, service-recovery procedures, and customer notification mechanisms to reduce the likelihood and impact of similar incidents in the future.

   provider

Corrections

None so far.

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