Degraded Data Collection

What to do

• Check whether you use Loggly Data Collection & Storage. 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 3h 48m it lasted.

  Anything that failed between 2026-10-06 12:16 UTC and 2026-10-06 16:04 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 7

1. investigatingOct 6, 2026, 12:16 PM UTC

   We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using certain ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. We will provide an update within the hour.

   provider

2. investigatingOct 6, 2026, 12:17 PM UTC

   We are continuing to investigate this issue.

   provider

3. investigatingOct 6, 2026, 1:19 PM UTC

   We are continuing to investigate this issue.

   provider

4. identifiedOct 6, 2026, 1:42 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

5. identifiedOct 6, 2026, 2:42 PM UTC

   We are continuing to work on a fix for this issue.

   provider

6. identifiedOct 6, 2026, 3:42 PM UTC

   We are continuing to work on a fix for this issue.

   provider

7. resolvedOct 6, 2026, 4:04 PM 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.