LogRocket Status: How to Check If LogRocket Is Down Right Now (2026)
Updated July 2026 · 6 min read · By API Status Check
Quick Answer: Check LogRocket Status Now
LogRocket is a frontend monitoring platform that combines session replay, error tracking, and performance monitoring so engineering teams can see exactly what a user experienced when something broke. Like PostHog, LogRocket ingests data client-side and processes it asynchronously — a delay in your dashboard doesn't always mean an outage, but a prolonged gap usually does.
How LogRocket Data Flows (and Where It Can Break)
- • The LogRocket snippet runs in the visitor's browser
- • Buffers DOM mutations, console logs, network requests
- • Uploads batched data on interval and on page unload
- • Can be blocked by ad blockers or strict CSP rules
- • Ingestion API accepts uploaded session data
- • Processing pipeline renders replayable sessions
- • Dashboard queries indexed session and error data
- • Check status.logrocket.com for pipeline health
Understanding LogRocket's Status Page (status.logrocket.com)
LogRocket operates status.logrocket.com to track their infrastructure components. Because session capture happens in the browser and uploads asynchronously, ingestion and dashboard rendering are tracked as separate systems.
Session Ingestion
The API endpoint that receives uploaded session recordings from the browser SDK. If degraded, sessions may queue on the client and upload late, or be dropped entirely if the browser tab closes before the upload completes.
Error Tracking
Captures uncaught exceptions, console errors, and network failures. Runs on the same ingestion pipeline as session data but can surface issues independently — errors may stop appearing while session replay keeps working.
Dashboard & Search
The web app used to browse and search sessions. A slow dashboard doesn't mean data is being lost — sessions are usually still ingesting and processing in the background even if search is degraded.
Recording Playback
The service that reconstructs and streams a recorded session for playback. Separate from ingestion — new sessions can capture successfully while playback of past sessions is temporarily unavailable.
Integrations
Webhook and third-party integrations (Slack, Jira, Sentry, Datadog). Integration failures don't affect core session capture or error tracking, only the automated actions triggered from them.
API
The REST API used for programmatic session lookup and custom event tracking. API degradation affects backend integrations more than the standard browser SDK capture path.
Diagnosing LogRocket Capture Issues
Most "LogRocket is down" reports are actually snippet, ad-blocker, or CSP configuration issues rather than a real outage. Run these checks first.
LogRocket Diagnostic Checklist
# 1. Confirm the SDK loaded in the browser console
window.LogRocket
# Should return an object, not undefined
# 2. Check the Network tab for upload requests
Filter requests for: r.lr-in.com OR r.logrocket.io
# Should show 200 responses on page unload
# 3. Verify init runs before other tracking scripts
LogRocket.init('app-id/project-name')
# Must run first — late init misses early session data
# 4. Check for ad-blocker interference
Test in an incognito window with extensions disabled
# 5. Verify Content-Security-Policy allows LogRocket domains
connect-src should include *.lr-in.com *.logrocket.io
Common LogRocket Failure Causes That Aren't Outages
- 🔴 Ad blockers and privacy extensions: uBlock Origin, Privacy Badger, and similar tools frequently block session recording scripts by default. This affects a meaningful share of real users, not just your testing.
- 🔴 Late script initialization: If LogRocket.init() runs after other analytics scripts or deep in your app's render tree, early session activity is lost even though later activity captures fine.
- 🔴 Strict Content-Security-Policy: A CSP that doesn't whitelist LogRocket's ingestion domains will silently block uploads — no console error is always shown, so check the Network tab directly.
- 🔴 Sampling rate configuration: If you've configured session sampling below 100%, "missing" sessions may simply be the ones that weren't sampled, not a capture failure.
- 🔴 Single-page app route changes: Some SPA routers can interfere with LogRocket's DOM mutation observer after client-side navigation. Verify sessions capture correctly across route transitions, not just on initial load.
Monitor the pages that load LogRocket from outside your network
External uptime monitoring catches script-loading failures and CDN issues before they silently break session capture for real users. Better Stack has a free plan.
Try Better Stack Free →What LogRocket Status Colors Mean
Common LogRocket Issues and What They Mean
"Sessions stuck at "Processing" for a long time"Session processing normally completes within a few minutes of upload. If a session stays in "Processing" for over 30 minutes, check the Session Ingestion component on status.logrocket.com — this usually indicates a backend processing delay rather than a client-side capture issue."Recording shows blank or broken layout"This is typically a DOM serialization issue, not an outage. Check for iframes, canvas elements, or shadow DOM content that LogRocket may not fully capture by default — some of these require explicit configuration to record correctly."Console errors not appearing in session"Verify console capture is enabled in your LogRocket.init() config (console.isEnabled option). Also check that error boundaries in your framework aren't swallowing exceptions before they reach the global error handler LogRocket listens to."Network requests missing from session"Check your network sanitization configuration — LogRocket lets you redact or exclude specific requests, and overly broad exclusion rules can hide requests you actually want to see. Also confirm the request isn't same-origin to a domain excluded by CORS restrictions."LogRocket dashboard showing stale data"Refresh and check status.logrocket.com for a Dashboard component incident. If the status page shows all green, clear your browser cache — dashboard search indexes can occasionally lag behind ingestion by a few minutes under normal operation.Frequently Asked Questions
Where is the official LogRocket status page?
LogRocket's official status page is status.logrocket.com. It breaks down status by component: Session Ingestion, Error Tracking, Dashboard, Recording Playback, Integrations, and API. Subscribe there for email or webhook alerts on incidents.
If LogRocket was down, did I lose session recordings?
It depends on when the outage occurred. LogRocket buffers session data client-side and uploads on interval and page unload — brief outages may just delay uploads until the ingestion API recovers. Prolonged outages, or a browser tab closing before the connection recovers, can cause permanent data loss for that session.
Why do ad blockers cause LogRocket to look 'down' when it isn't?
Ad blockers and privacy extensions like uBlock Origin commonly block session recording and analytics scripts by default, including LogRocket's. This affects a real, non-trivial percentage of your visitors — it's a client-side blocking issue, not a LogRocket outage, and it won't show up on status.logrocket.com.
How is LogRocket different from Sentry for outage purposes?
Sentry focuses primarily on error and exception tracking, while LogRocket combines session replay with error tracking and performance monitoring. Many teams run both together. If Sentry is reporting an error but LogRocket has no matching session, check whether the error occurred before LogRocket finished initializing on the page.
How do I get alerts when LogRocket goes down?
Subscribe to updates at status.logrocket.com for official incident notifications. For an independent signal, set up external uptime monitoring on the pages that load the LogRocket snippet — this can catch script-loading or CDN failures that don't originate from LogRocket's own infrastructure.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time LogRocket goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for LogRocket + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial