We started checking Rollbar on November 2, 2026, which is 8 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Rollbar reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Rollbar's own status page declared. Below it, any public chatter we saw about Rollbar and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Rollbar's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Rollbar in the last 24 hours, which is not evidence that nothing is wrong.
Rollbar's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Rollbar's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Rollbar next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.88%
868
US-West
100.00%
711
Europe
100.00%
666
Asia-Pacific
100.00%
399
Their declared record
Rollbar's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Currently experiencing LOGIN issues Partial outage
May 18, 2026, 8:50 PM UTC to May 19, 2026, 8:59 AM UTC (12h 9m)resolved
their latest update (May 19, 2026, 8:59 AM UTC): We have fully rolled this back and applied the updated image.
Item Processing impact for RUBY and PHY SDKs All systems operational
May 8, 2026, 9:30 PM UTC to May 8, 2026, 9:30 PM UTC (0 min)resolved
their latest update (May 8, 2026, 9:30 PM UTC): Earlier today we identified and resolved an issue impacting customers using our PHP and Ruby SDKs. A backend API change deployed on Friday 5/8/26 ~2:30PM PT inadvertently broke request parsing for certain payloads sent with the Ruby and PHP SDKs. As a result, occurrences sent dur…
Apr 20, 2026, 5:51 PM UTC to Apr 20, 2026, 8:22 PM UTC (2h 31m)resolved
their latest update (Apr 20, 2026, 8:22 PM UTC): Pipeline processing is back to normal levels for all occurrence variants. This incident has been resolved.
Apr 7, 2026, 9:02 AM UTC to Apr 7, 2026, 4:52 PM UTC (7h 50m)resolved
their latest update (Apr 7, 2026, 4:52 PM UTC): This incident was resolved. Rollbar processing pipeline latency (measured at p99) was elevated above our 30-second p99 SLO today during the following windows:
02:02AM - 02:35AM PDT: 30s - 7.0 minutes latency
06:02AM - 07:03AM PDT: 30s - 3.9 minutes latency
08:00AM - 09:02AM PDT:…
Web app errors, primarily on Item DetailPartial outage
Mar 6, 2026, 3:59 PM UTC to Mar 6, 2026, 4:57 PM UTC (58 min)resolved
their latest update (Mar 6, 2026, 4:57 PM UTC): This incident has been resolved.
Web application page loading issuesMinor incident
Jan 27, 2026, 9:20 AM UTC to Jan 27, 2026, 10:56 AM UTC (1h 36m)resolved
their latest update (Jan 27, 2026, 10:56 AM UTC): Our third-party provider has successfully implemented a fix. We have verified that all affected services are now fully operational.
We will continue to monitor the situation closely to ensure continued stability. Thank you for your patience.
Showing the 10 most recent of 25 incidents Rollbar has declared in the history we hold.
These entries are Rollbar's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Rollbar's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.