CheckUpstream does not yet run an independent probe against LogRocket, so no availability figure is published for it — only LogRocket's own disclosure record below. 2 incidents were recorded in the past 12 months; the most recent resolved 77 days ago after 3 hours. Status signals are polled from LogRocket's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against LogRocket yet, so we publish no availability figure for it. What follows is LogRocket's own disclosure record, which is a different thing.
Vendor disclosed: 1 incident · 90 of 90 days with none posted · 0m of declared impact
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by LogRocket
7d
100.000%
30d
100.000%
90d
100.000%
180d
100.000%
1y
100.000%
Does LogRocket actually matter to you?
A LogRocket outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Live LogRocket status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/logrocket)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
LogRocket is currently Operational. CheckUpstream tracks LogRocket in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is LogRocket down" view? See the LogRocket Live status page.
LogRocket's last resolved incident started 77 days ago and lasted 3h 25m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against LogRocket yet, and the only other figure available would be derived from LogRocket's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add LogRocket to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll LogRocket's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.