Is Rollbar Down?

No — Rollbar is up

Reachable from all 8 checked regions

Average response time: 354ms

Last checked 33 minutes ago · checks run every 6 hours

Official status page: https://status.rollbar.com

Rollbar uptime

100%

Last 7 days

100%

Last 30 days

99.90%

Last 90 days

336ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 32 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

30-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg

375ms

DNS 52ms TCP 1ms TLS 12ms TTFB 345ms

dfw

294ms

DNS 85ms TCP 1ms TLS 7ms TTFB 265ms

ewr

248ms

DNS 23ms TCP 2ms TLS 8ms TTFB 217ms

fra

333ms

DNS 15ms TCP 2ms TLS 10ms TTFB 299ms

gru

517ms

DNS 179ms TCP 2ms TLS 10ms TTFB 484ms

iad

269ms

DNS 31ms TCP 2ms TLS 11ms TTFB 235ms

jnb

520ms

DNS 12ms TCP 0ms TLS 7ms TTFB 436ms

lax

279ms

DNS 35ms TCP 1ms TLS 8ms TTFB 246ms

What Rollbar does

Rollbar is an error monitoring service that collects exceptions and crashes from applications, groups them into items and links them to releases and session replays. Engineering teams route it into alerting and use it to decide whether a deploy introduced a regression. It sits in the path of noticing problems rather than serving traffic, so its own outage is a quiet one.

What an outage looks like

Errors stop appearing in the dashboard, which reads as an unusually calm application rather than as a failure. Alerts to Slack, PagerDuty or email stop firing. Deploy tracking shows no new releases. The client-side rollbar.min.js snippet may fail to load, which can slow page rendering in the browser if the page loads it in a blocking way.

What to do about it

status.rollbar.com separates the Web Tier from the API tier at api.rollbar.com, the processing pipeline, external notification services and the rollbar.min.js asset, so an ingestion problem is distinguishable from a dashboard one. That distinction decides what you do: if the API tier is accepting events and only the Web Tier is down, nothing is being lost. Treat a silent dashboard as unproven, not as good news.

Is it down for everyone, or just you?

If this page says Rollbar is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Rollbar outage FAQ

No errors are showing. Is my app healthy or is Rollbar down?

Assume nothing until you check, because the two look identical from the dashboard. Rollbar lists the API tier at api.rollbar.com and the processing pipeline separately from the Web Tier, and any of them can break the flow. Confirm against a second signal such as your own logs or request error rates before concluding the application is fine.

Will I lose errors reported during an outage?

It depends where the break is. If the API tier is accepting events and only the pipeline or dashboard is behind, occurrences are captured and appear late. If ingestion itself is down, the SDK cannot deliver and those occurrences are gone. Rollbar's status page distinguishes the two, which is the fastest way to tell which case you are in.

Do Rollbar alerts still reach Slack and PagerDuty during an incident?

Not necessarily. External notification services is its own component on the status page, so alert delivery can fail while error collection continues normally. Errors then pile up unseen until someone opens the dashboard. During an incident, watch your application directly rather than waiting for a Rollbar alert to tell you something is wrong.

Rollbar's JavaScript snippet will not load. Does that break my site?

It should not break the page, but it can slow rendering if the snippet is loaded in a blocking way. Rollbar tracks rollbar.min.js as its own status component precisely because it is served to your visitors. Loading it asynchronously limits the effect of a slow or unreachable asset, which is worth checking before the next incident rather than during one.

Does a Rollbar outage affect deploys?

It does not stop them, but it removes the safety net. Deploy tracking and release linking go quiet, so a regression introduced during the incident will not surface where you normally look for it. Postponing a risky deploy until error collection is confirmed working is the cheaper option whenever the change is not urgent.

How we measure this

We request Rollbar's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Rollbar publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Rollbar goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required