- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on LogRocket. 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 0m it lasted.
Anything that failed between 2026-07-22 01:31 UTC and 2026-07-22 01:00 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 1
- resolved
Between 8:50pm and 9:10pm America/New_York on July 21st, there were availability blips during an upgrade of our nginx proxy layer. SDK clients will have retried during this event and we recovered from a backlog by 9:30pm.
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-71391986f7
Is LogRocket still down?
No, this incident was resolved 2026-07-22 01:00 UTC. For LogRocket's live state, see https://down.guide/logrocket.
How long did it last?
0m, from 2026-07-22 01:31 UTC to 2026-07-22 01:00 UTC, by the times LogRocket posted.
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.