Is LogRocket Down? How to Check LogRocket Status Right Now

LogRocket is the session replay and frontend monitoring platform that engineering and product teams rely on to understand exactly what users experienced before a bug report or support ticket. When LogRocket is working, sessions record automatically, errors link to replays, and product teams can watch a user's exact journey through any issue. When LogRocket goes down, new sessions stop recording, the replay index falls behind, and errors in your application go unobserved — you're blind to production problems until users tell you.

Here's how to determine whether LogRocket is down, which component is failing, and how to maintain frontend observability when it degrades.

Is LogRocket Down Right Now?

Check these sources in order:

1. Statusfield — LogRocket status — real-time monitoring of LogRocket's platform availability.
2. Twitter/X — search LogRocket down or LogRocket not recording sorted by Latest. Frontend engineering teams notice session recording failures quickly.
3. Downdetector — useful for confirming widespread user reports.

What Actually Breaks During a LogRocket Outage

LogRocket separates data ingestion, replay storage, error processing, and the dashboard into distinct subsystems.

Common LogRocket Issues and What They Mean

Developer Impact: What Happens to the LogRocket SDK During an Outage

The LogRocket browser SDK records session data locally and periodically flushes it to LogRocket's ingestion endpoint. Understanding the SDK's behavior during an outage helps you set expectations.

Ingestion endpoint down: The SDK will attempt to send data and fail. Depending on your SDK version and configuration, it may buffer some data in memory for retry, but this buffer is not persisted — if the user navigates away or closes the tab, buffered data is lost. Sessions from the outage window will have gaps or be missing entirely.

SDK CDN down: If the script tag loading cdn.lr-in.com fails, LogRocket never initializes. No data is captured for the duration of the outage. This is a silent failure — no console errors will appear from your application code, and you won't know sessions weren't recorded until you check the dashboard.

Dashboard down with ingestion healthy: Data continues to be recorded and stored. When the dashboard recovers, sessions from the outage window will appear normally. This is the least impactful scenario.

Checking LogRocket SDK Health in Your Application

Add a simple health check to detect LogRocket initialization failures:

// Check if LogRocket loaded and initialized successfully
function checkLogRocketHealth(): void {
  // Wait for SDK to initialize (it loads asynchronously)
  setTimeout(() => {
    if (typeof window.LogRocket === 'undefined') {
      console.warn('[monitoring] LogRocket SDK did not load — possible CDN issue');
      // Alert your monitoring system
      metrics.increment('logrocket.sdk.load_failure');
      return;
    }
 
    // SDK loaded — check if session is active
    const sessionURL = window.LogRocket.sessionURL;
    if (!sessionURL) {
      console.warn('[monitoring] LogRocket session not started');
    } else {
      console.info('[monitoring] LogRocket active:', sessionURL);
    }
  }, 5000); // 5 seconds after page load
}

Maintaining Observability When LogRocket Is Down

Frontend monitoring has no perfect fallback, but you can reduce the blind spot.

Keep browser console errors in your logging pipeline. If your application sends window.onerror events to your backend or a secondary logger (Sentry, Datadog), those will still capture JavaScript errors even when LogRocket is down. LogRocket replays add context, but error data is not exclusively in LogRocket.

Check your error tracking redundancy. Most teams run LogRocket alongside another error tracker (Sentry, Bugsnag, Rollbar). Verify that your secondary error tracker is active and capturing during a LogRocket outage — it won't have session replay, but it will have stack traces and error counts.

Communicate outage windows to support. If LogRocket is down during a period when users report bugs, note the outage window so support and product teams know that replay data for that period may be incomplete. Don't spend time searching for replays that won't exist.

How to Get Instant LogRocket Outage Alerts

When LogRocket's ingestion is down, your application is flying blind. Engineering teams need to know immediately — not after a post-mortem reveals a 6-hour gap in session recording.

Monitor LogRocket on Statusfield and get alerted the moment LogRocket's status changes. Route alerts to your engineering Slack channel or ops tool so no one is surprised by a gap in replay coverage.

Start monitoring LogRocket → — free, no credit card required.

Frequently Asked Questions

Is LogRocket down for everyone or just me?

Check statusfield.com/services/logrocket. If LogRocket shows operational and sessions aren't appearing in your dashboard, the issue may be specific to your project configuration — check your SDK initialization code, verify your project API key, and confirm the LogRocket script is loading without network errors in your browser's DevTools.

Why aren't new sessions showing up in the LogRocket dashboard?

There's typically a few minutes of ingestion delay before sessions appear. If sessions are missing for more than 15-20 minutes, check statusfield.com/services/logrocket for ingestion or dashboard status. Also check your browser's Network tab for failed requests to LogRocket's ingestion endpoint (typically r.lr-in.com).

LogRocket replays won't load — is this an outage?

If replays spin indefinitely or fail to play, check statusfield.com/services/logrocket for replay playback status. If the service is operational, try a hard refresh, a different browser, or check if you have a VPN or ad blocker that might be blocking LogRocket's CDN. Replays are large and can occasionally timeout on slow connections.

Are sessions lost during a LogRocket outage?

Sessions from an ingestion outage window are typically lost — the SDK can buffer a limited amount of data in memory, but once the tab closes, unflushed data is gone. Sessions from before the outage are safe (already persisted). If the dashboard was down but ingestion was healthy, sessions are intact and will appear once the dashboard recovers.

LogRocket SDK is throwing console errors — do I need to fix them?

LogRocket SDK console errors (like failed fetch attempts to ingestion endpoints) are usually transient and resolve when Mailgun recovers. They don't affect your application's functionality — LogRocket is designed to be non-blocking. However, persistent SDK errors that continue after LogRocket recovers may indicate a misconfiguration (wrong API key, wrong endpoint region) — check your initialization code.

How do I get alerted when LogRocket goes down?

Set up LogRocket monitoring on Statusfield. You'll get an alert the moment LogRocket's status changes — giving your engineering team advance notice before discovering a replay gap during the next bug investigation.

Published: July 4, 2026. Check current LogRocket status →