Is Rollbar Down?

No — Rollbar is up

Rollbar's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 372 ms

Right now

The verdict is the worse of these two. How we decide

Rollbar's status page

status.rollbar.com · read 2 minutes ago · checked every 3 minutes

Operational

Rollbar's components, as its status page reports them
Component	Status
Web Application (app.rollbar.com)	Operational
Homepage (rollbar.com)	Operational
API Tier (api.rollbar.com)	Operational
Core Processing Pipeline	Operational
iOS Symbolication processing pipeline	Operational
Source map processing pipeline	Operational
Proguard processing pipeline	Operational
Mailgun SMTP	Operational
Mailgun Outbound Delivery	Operational
rollbar.min.js	Operational
SCIM and SSO	Operational
Rollbar Docs	Operational

Open their status page

FlareWarden checks

rollbar.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 372 ms
Checked: 4 hours ago

By region

Ashburn reachable, 273 ms
Dallas reachable, 239 ms
Frankfurt reachable, 329 ms
Johannesburg reachable, 681 ms
London reachable, 366 ms
Los Angeles reachable, 262 ms
Newark reachable, 294 ms
São Paulo reachable, 533 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	35 ms	0 ms	10 ms	244 ms
Dallas	32 ms	2 ms	10 ms	212 ms
Frankfurt	31 ms	2 ms	12 ms	305 ms
Johannesburg	161 ms	1 ms	8 ms	561 ms
London	34 ms	4 ms	11 ms	338 ms
Los Angeles	15 ms	3 ms	10 ms	234 ms
Newark	38 ms	2 ms	11 ms	264 ms
São Paulo	162 ms	2 ms	10 ms	505 ms

We check that rollbar.com loads, not every feature behind it. Test it yourself

History

Incidents Rollbar reported

Since Oct 22, 16 days · from status.rollbar.com

Incidents: 1
Major or critical: 0
Median to resolve: 12m

Increased occurrence processing pipeline latency
minor · Oct 28
lasted 12m

Rollbar website availability

Measured by FlareWarden · rollbar.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 397ms

Last 30 days

78-day clean streak

Oct 8 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of rollbar.com from multiple regions every 6 hours. Rollbar's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 78 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Rollbar itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Rollbar goes down

We check Rollbar every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required