- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Alerts
- Down Index
- 32of 100
What to do
Check whether you use Loggly Alerts. 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 3h 46m it lasted.
Anything that failed between 2021-02-13 09:18 UTC and 2021-02-13 13: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 4
- investigating
We are currently investigating 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-63060f22e8
Is Loggly still down?
No, this incident was resolved 2021-02-13 13:04 UTC. For Loggly's live state, see https://down.guide/providers/loggly.
How long did it last?
3h 46m, from 2021-02-13 09:18 UTC to 2021-02-13 13:04 UTC, by the times Loggly posted.
What was affected?
Loggly named Alerts.
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.