Vendor record
LogRocket
Checked
Front door check counts and LogRocket’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against LogRocket in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every LogRocket product, region or your app worked.
How we count front door checksLogRocket says
Incident posts from LogRocket’s status page, with its titles, impact levels and times. They say what LogRocket chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
2
incidents LogRocket posted, last 180 days
Most recent records · all dates
Delayed analytics ingestion and alerts
MinorLogRocket’s postStarted, per LogRocket
Closed in our record(3h 25m)
Dashboard instability
MajorLogRocket’s postStarted, per LogRocket
Closed in our record(47m)
Your code, your dependencies
See which of your code paths call LogRocket
Connect GitHub or GitLab to find where your public or private repository uses LogRocket. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add LogRocket status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is LogRocket currently down?
LogRocket's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did LogRocket last have an outage?
The most recent closed incident record began 123 days ago and spans 3h 25m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for LogRocket?
No. CheckUpstream does not run front door checks against LogRocket. The incident history on this page is what LogRocket reported, not a measure of how often it was available.
How do I monitor LogRocket in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track LogRocket?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.