Is Rollbar Down? How to Check Rollbar Status Right Now

Rollbar is the error tracking and monitoring platform that engineering teams depend on to catch, group, and resolve production errors in real time. When Rollbar is working, exceptions flow from your application into a searchable, grouped feed — with stack traces, user context, and deployment correlations. When Rollbar degrades, your error pipeline goes silent: exceptions are thrown in production, but no one is paged, no one sees the error count rising, and the first sign of a problem is user reports or a traffic drop.

Here's how to determine whether Rollbar is down, which component is failing, and how to protect your error visibility when it degrades.

Is Rollbar Down Right Now?

Check these sources in order:

1. Statusfield — Rollbar status — real-time monitoring of Rollbar's platform availability.
2. Twitter/X — search Rollbar down or Rollbar not receiving errors sorted by Latest.
3. Downdetector — useful for confirming widespread user reports.

What Actually Breaks During a Rollbar Outage

Rollbar separates error ingestion, processing, storage, and notification into distinct subsystems.

Common Rollbar Issues and What They Mean

Building a Rollbar Integration That Survives Outages

Use the SDK's built-in queue and retry

The official Rollbar SDKs (rollbar.js, rollbar-python, rollbar-ruby, etc.) include retry logic and local queuing. Make sure you're using the official SDK rather than raw HTTP calls — the SDK will buffer items and retry failed deliveries, reducing data loss during short outages.

// rollbar.js — configure queue behavior
import Rollbar from 'rollbar';
 
const rollbar = new Rollbar({
  accessToken: process.env.ROLLBAR_SERVER_TOKEN,
  captureUncaught: true,
  captureUnhandledRejections: true,
  retryInterval: 5000,    // Retry every 5 seconds
  maxRetries: 5,          // Retry up to 5 times
  // Items are queued locally if the network request fails
});

Handle SDK initialization failures gracefully

If Rollbar's CDN or API is unreachable during startup, your application should degrade gracefully rather than throwing errors of its own:

let rollbar: Rollbar | null = null;
 
try {
  rollbar = new Rollbar({ accessToken: process.env.ROLLBAR_TOKEN });
  console.info('[monitoring] Rollbar initialized');
} catch (err) {
  console.warn('[monitoring] Rollbar failed to initialize — falling back to console logging');
}
 
// Safe wrapper — works with or without Rollbar
function captureError(error: Error, context?: Record<string, unknown>): void {
  if (rollbar) {
    rollbar.error(error, context);
  } else {
    console.error('[untracked error]', error, context);
  }
}

Set up a secondary error sink

For critical applications, route errors to a secondary sink when Rollbar is unavailable. This can be as simple as writing errors to your application's own logging pipeline or a secondary error tracker:

// Secondary error logging — fires when Rollbar is unreachable
function logErrorFallback(error: Error, context?: Record<string, unknown>): void {
  // Log to your application's structured logger (Datadog, Logtail, etc.)
  logger.error('untracked_error', {
    message: error.message,
    stack: error.stack,
    ...context,
    rollbar_available: false,
  });
}

What Happens to Errors During a Rollbar Outage

Short ingestion outage (< 15 minutes): The Rollbar SDK queues items locally. When ingestion recovers, queued items are flushed. You may see a delayed spike in error counts as the backlog processes.

Extended ingestion outage (> 15 minutes): Items that exceed the SDK's in-memory queue or that were sent during browser page navigations (which clear memory) are permanently lost. The error gap in your dashboard will be real.

Processing outage with healthy ingestion: Items are accepted by Rollbar's API but not yet grouped or indexed. They'll appear in the dashboard when processing recovers — no data loss, but a delay.

Notification outage with healthy processing: Errors are tracked and visible in the dashboard, but alerts don't fire. This is operationally significant: on-call engineers aren't paged for new issues. Check your Rollbar dashboard manually if you suspect a notification outage.

How to Get Instant Rollbar Outage Alerts

When Rollbar's notifications are down, your on-call rotation loses its primary paging path. When ingestion is down, errors are disappearing into a void. Your team needs to know about Rollbar outages as quickly as they'd know about any other production incident.

Monitor Rollbar on Statusfield and get alerted the moment Rollbar's status changes. Route the alert to the same channel as your other production alerts so Rollbar outages are treated with the same urgency as the errors they're supposed to catch.

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

Frequently Asked Questions

Is Rollbar down for everyone or just me?

Check statusfield.com/services/rollbar. If Rollbar shows operational and errors aren't appearing, the issue may be specific to your project token, rate limits, or SDK configuration. Check your application's network requests for failed calls to the Rollbar items API (typically api.rollbar.com/api/1/item/) and verify your access token is valid in the Rollbar dashboard.

Why isn't Rollbar receiving errors from my application?

Several things can cause this: Rollbar's ingestion endpoint is down (check statusfield.com/services/rollbar), your access token is invalid or rate-limited, the SDK isn't initialized (check browser network requests), or a firewall / CSP policy is blocking the request to api.rollbar.com. Check your application's network tab for failed Rollbar requests as the first diagnostic step.

Rollbar is receiving errors but notifications aren't firing — what's happening?

Notification delivery is a separate Rollbar subsystem. Check statusfield.com/services/rollbar for notification status. If Rollbar shows healthy, verify your notification rules are correctly configured and your Slack / PagerDuty integration is still connected. Slack and PagerDuty permission changes on the downstream side can silently break Rollbar integrations.

Are errors lost during a Rollbar outage?

Errors queued by the official Rollbar SDK may be retried and delivered when the service recovers. However, errors that exceed the in-memory queue or are generated during browser navigations (which clear memory) are lost. For long outages, assume there's a data gap and rely on your application logs for error data during the window. Check statusfield.com/services/rollbar to understand when the outage started and ended.

How do I check if Rollbar is the cause vs. my application's network?

Check statusfield.com/services/rollbar first. If Rollbar is operational, open your browser's DevTools → Network tab, filter by api.rollbar.com, and trigger a test error in your application. If the request fails with a network error or returns a 5xx, Rollbar's API is the problem. If the request doesn't appear at all, the SDK isn't initializing or a CSP policy is blocking the request.

How do I get alerted when Rollbar goes down?

Set up Rollbar monitoring on Statusfield. You'll get an alert the moment Rollbar's status changes — so your team knows to check the dashboard manually and treat any new user-reported errors with extra urgency during the outage window.

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