- Level
- confirmed
- Worst impact
- Degraded
- Components
- Alerts
- Down Index
- 23of 100
What to do
Check whether you use LogRocket Alerts. 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 6h 10m it lasted.
Anything that failed between 2022-03-30 15:39 UTC and 2022-03-30 21:48 UTC may need a replay.Subscribe to LogRocket's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=logrocket works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from LogRocket 3
- investigating
We are currently investigating an issue with our primary search cluster that is causing delays in processing some search data. Alerting is also impacted at this time. Session ingestion is not impacted and we continue to record new sessions.
provider
- monitoring
We've implemented some fixes and are waiting for a backlog to process while monitoring.
provider
- resolved
The 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-b9a8b0a93b
Is LogRocket still down?
No, this incident was resolved 2022-03-30 21:48 UTC. For LogRocket's live state, see https://down.guide/logrocket.
How long did it last?
6h 10m, from 2022-03-30 15:39 UTC to 2022-03-30 21:48 UTC, by the times LogRocket posted.
What was affected?
LogRocket named Alerts.
What caused it?
LogRocket hasn't published a root cause. If it does, it shows here.
Where does this come from?
LogRocket's official status page, https://status.logrocket.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.