Rollbar Outage History

32 incidents recorded over the last 365 days, 32 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Rollbar status99.41% uptime history

Every Recorded Rollbar Incident

Rollbar incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 24, 2026Database maintenace.Maintenance has started23h 48mResolved
Aug 20, 2026Database and pipeline maintenanceMaintenance has started90h 21mResolved
Aug 19, 2026Database MaintenanceMaintenance has started15h 33mResolved
Aug 19, 2026 During the maintenance window, we will perform a series of routine tasks on our databasesMaintenance has started19h 35mResolved
Aug 18, 2026Database maintenance Maintenance has started15h 54mResolved
Aug 12, 2026Database maintenance We need to apply some maintenance to our DB cluster it will impact the pipeline briefly, apologies for the inconvenience this will cause.15h 27mResolved
Jul 21, 2026During the maintenance window, we will perform a series of routine tasks on our databasesMaintenance has started318h 47mResolved
Jul 15, 2026During the maintenance window, we will perform a series of routine tasks on our databasesMaintenance has started461h 31mResolved
Jul 14, 2026DB Maintenance Maintenance has started476h 39mResolved
Jul 14, 2026During the maintenance window, we will perform a series of routine tasks on our databasesMaintenance has started486h 35mResolved
Jul 10, 2026During the maintenance window, we will perform a series of routine tasks on our databasesDuring the maintenance window, we will perform a series of routine tasks on our databases581h 14mResolved
Jul 8, 2026During the maintenance window, we will perform a series of routine tasks on our databasesMaintenance has started629h 17mResolved
Jul 7, 2026During the maintenance window, we will perform a series of routine tasks on our databasesDuring the maintenance window, we will perform a series of routine tasks on our databases653h 50mResolved
Jul 6, 2026During the maintenance window, we will perform a series of routine tasks on our databasesDuring the maintenance window, we will perform a series of routine tasks on our databases681h 36mResolved
Jul 3, 2026DB MaintenanceDuring the maintenance window, we will perform a series of routine tasks on our databases752h 9mResolved
Jul 1, 2026 During the maintenance window, we'll perform a series of routine tasks on our databases.Maintenance has started796h 29mResolved
Jun 30, 2026During the maintenance window, we'll perform a series of routine tasks on our databases.Maintenance has started826h 36mResolved
Jun 25, 2026Increased occurrence processing pipeline latencyIncident resolved29 minResolved
Jun 25, 2026DB MaintenanceDuring the maintenance window, we will perform a series of routine tasks on our databases941h 53mResolved
Jun 15, 2026database maintenance Maintenance has started1177h 16mResolved
Jun 3, 2026Database Maintenance Maintenance has started1462h 51mResolved
May 18, 2026Currently experiencing LOGIN issues We have fully rolled this back and applied the updated image.12h 8mResolved
May 9, 2026Item Processing impact for RUBY and PHY SDKs 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…-1325 minResolved
Apr 20, 2026Increased occurrence processing pipeline latencyPipeline processing is back to normal levels for all occurrence variants. This incident has been resolved.2h 31mResolved
Apr 8, 2026Increased processing pipeline latencyThis 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 -…-667 minResolved
Mar 6, 2026Web app errors, primarily on Item DetailThis incident has been resolved.57 minResolved
Jan 27, 2026Web application page loading issuesOur 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…1h 36mResolved
Nov 20, 2025Database Maintenance The update took a lot longer due to the mass of data involved. However it is now complete and we apologize for any impact this made.9h 43mResolved
Nov 18, 2025Web application page loading issuesIncident resolved. Cloudflare applied a patch and all loosk working ok again.3h 27mResolved
Oct 20, 2025Increased occurrence processing pipeline latencyOur services have returned to normal operation. Sorry for any inconvenience caused.8h 6mResolved
Oct 20, 2025Service Disruption Across InfrastructureOur cloud provider has fixed the networking issues they were experiencing.3h 43mResolved
Sep 3, 2025Elevated API error rate**# Incident Report ## Summary of the Incident and Impact** From 2025-09-03 05:35 PT until approximately 14:03 PT, the Rollbar ingestion API) served a high rate of 502 errors because a particular traffic pattern…4h 10mResolved

How to Read This Rollbar Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Rollbar acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Rollbar outage in this window ran 60d 22h, against a mean recovery of 14d 13h. If you depend on Rollbar in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.