Loggly: Searching of historical data degraded

What to do

Check whether you use Loggly Search Availability. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 6h 21m it lasted.
Anything that failed between 2021-03-15 18:45 UTC and 2021-03-16 01:06 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.

investigatingMar 15, 2021, 6:45 PM UTC
Small subset of customers can see gaps in searching historical data. All data continues to be indexed and stored correctly. We are working on resolving the issue.
provider
identifiedMar 15, 2021, 7:21 PM UTC
The issue has been identified and a fix is being implemented.
provider
resolvedMar 16, 2021, 1:06 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Loggly still down?

No, this incident was resolved 2021-03-16 01:06 UTC. For Loggly's live state, see https://down.guide/providers/loggly.

How long did it last?

6h 21m, from 2021-03-15 18:45 UTC to 2021-03-16 01:06 UTC, by the times Loggly posted.

What was affected?

Loggly named Search Availability.

What caused it?

Loggly hasn't published a root cause. If it does, it shows here.

Where does this come from?

Loggly's official status page, https://status.loggly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.