- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Indexing Data
- Down Index
- 30of 100
What to do
Check whether you use Loggly Indexing Data. 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 1h 27m it lasted.
Anything that failed between 2023-08-23 19:13 UTC and 2023-08-23 20:40 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 4
- investigating
Our engineers have identified an issue with log ingestion starting at 11:54AM PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ab03aca25a
Is Loggly still down?
No, this incident was resolved 2023-08-23 20:40 UTC. For Loggly's live state, see https://down.guide/loggly.
How long did it last?
1h 27m, from 2023-08-23 19:13 UTC to 2023-08-23 20:40 UTC, by the times Loggly posted.
What was affected?
Loggly named Indexing Data.
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.