- Level
- confirmed
- Worst impact
- Degraded
- Components
- Session Collection, Alerts
- Down Index
- 23of 100
What to do
Check whether you use LogRocket Session Collection, 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 2h 45m it lasted.
Anything that failed between 2025-02-04 18:29 UTC and 2025-02-04 21:14 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 4
- investigating
We are investigating issues causing ingestion delays and performance issues loading the dashboard and metrics.
provider
- investigating
Dashboard performance should be improved. We are continuing to work with a vendor on identifying the root cause of our ingestion delays.
provider
- monitoring
We have identified a potential cause and observing significant improvements to ingestion delays. We are continuing to monitor.
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-e1cba385f1
Is LogRocket still down?
No, this incident was resolved 2025-02-04 21:14 UTC. For LogRocket's live state, see https://down.guide/logrocket.
How long did it last?
2h 45m, from 2025-02-04 18:29 UTC to 2025-02-04 21:14 UTC, by the times LogRocket posted.
What was affected?
LogRocket named Session Collection, 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.