- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard, Issues, Alerts
- Down Index
- 27of 100
What to do
Check whether you use LogRocket Dashboard, Issues, 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 9h 17m it lasted.
Anything that failed between 2023-05-25 16:25 UTC and 2023-05-26 01:42 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 an issue with secondary search indexing. Data collection and session replay are not impacted.
provider
- identified
We have identified a cause and are working towards a resolution.
provider
- monitoring
We have resolved the issue and anticipate the backlog of events to take 1 to to 2 hours to complete.
provider
- resolved
The backlog has been completely processed and all systems are now up to date.
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-55aad3a1a4
Is LogRocket still down?
No, this incident was resolved 2023-05-26 01:42 UTC. For LogRocket's live state, see https://down.guide/providers/logrocket.
How long did it last?
9h 17m, from 2023-05-25 16:25 UTC to 2023-05-26 01:42 UTC, by the times LogRocket posted.
What was affected?
LogRocket named Dashboard, Issues, 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.