Rollbar Outage History

Rollbar is up right now

Pingoru has recorded 18 incidents for Rollbar: 15 in the last 12 months and 2 in the last 90 days.

Source: status.rollbar.com

18incidents recorded
15last 12 months
2last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Rollbar in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026410 of 720 (1%)
May 2026212 of 744 (2%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202622 of 720 (0%)
October 202600 of 530 (0%)

Incidents, newest first

Minor September 16, 2026 Increased occurrence processing pipeline latency 26m Core Processing Pipeline, iOS Symbolication processing pipeline, Source map processing pipeline, Proguard processing pipeline

Started Sep 16, 2026, 09:45 AM UTC· resolved Sep 16, 2026, 10:11 AM UTC

  1. investigating Sep 16, 2026, 09:45 AM UTC

    We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.

  2. identified Sep 16, 2026, 09:48 AM UTC

    Root cause identified. Fix applied.

  3. monitoring Sep 16, 2026, 10:02 AM UTC

    Processing backlog. Issue solved.

  4. resolved Sep 16, 2026, 10:11 AM UTC

    Backlog drained, all processing nominal

Read the full incident report →

Minor September 1, 2026 Widespread incident impacting multiple parts of our platform caused by an incident within our cloud provider 1h 13m Core Processing Pipeline, iOS Symbolication processing pipeline, Source map processing pipeline, Proguard processing pipeline and 5 more

Started Sep 01, 2026, 03:39 PM UTC· resolved Sep 01, 2026, 04:53 PM UTC

  1. investigating Sep 01, 2026, 03:39 PM UTC

    We are currently experiencing an incident that is impacting multiple parts of the platform , we believe this is caused by an incident within our cloud provider. We are currently processing data but we are seeing some of our services such as WEB/API are potentially impacted. We will provide an update as we learn more about this issue, and we apologize for any inconvenience this might be causing.

  2. monitoring Sep 01, 2026, 03:59 PM UTC

    It appears that work has been done by our cloud provider which has resolved many of the issues we were experiencing but we will give this some more time while we monitor before resolving this issue.

  3. resolved Sep 01, 2026, 04:53 PM UTC

    We believe everything is now back to normal , sorry for the inconvenience caused.

Read the full incident report →

Minor May 18, 2026 Currently experiencing LOGIN issues 12h 8m

Started May 18, 2026, 08:50 PM UTC· resolved May 19, 2026, 08:59 AM UTC

  1. investigating May 18, 2026, 08:50 PM UTC

    We are investigating an issue with LOGIN at present, we are working on a resolution for this and will update accordingly.

  2. identified May 18, 2026, 08:51 PM UTC

    We are currently rolling back a recent change, and will update once that is in place.

  3. identified May 18, 2026, 08:54 PM UTC

    We have rolled back internally (manually) which appears to have resolved the issue. We are waiting for a code build to officially revert the change.

  4. resolved May 19, 2026, 08:59 AM UTC

    We have fully rolled this back and applied the updated image.

Read the full incident report →

Minor May 8, 2026 Item Processing impact for RUBY and PHY SDKs – Core Processing Pipeline, iOS Symbolication processing pipeline, Source map processing pipeline, Proguard processing pipeline and 2 more

Started May 08, 2026, 09:30 PM UTC· resolved May 08, 2026, 09:30 PM UTC

  1. resolved May 08, 2026, 09: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 during this window were rejected and not recorded. We rolled back the change this morning (5/9 at 8:30 am PT) and occurrence ingestion is back to normal. Unfortunately, occurrences that were dropped during the affected window, were not stored and cannot be recovered. We understand thats a gap in your observability and we take that seriously. We’re conducting a full postmortem and will publish details on our statue page. In the meantime if you’re still seeing issues or have questions, please don’t hesitate to reply here.

Read the full incident report →

Minor April 7, 2026 Increased processing pipeline latency –

Started Apr 07, 2026, 04:52 PM UTC· resolved Apr 07, 2026, 04:52 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 6, 2026 Web app errors, primarily on Item Detail 57m

Started Mar 06, 2026, 03:59 PM UTC· resolved Mar 06, 2026, 04:57 PM UTC

  1. identified Mar 06, 2026, 03:59 PM UTC

    We've identified a problem causing errors loading the Item Detail screen. We're working to deploy a fix.

  2. monitoring Mar 06, 2026, 04:23 PM UTC

    Fix has been released and the error rate has dropped to zero. We'll continue to monitor.

  3. resolved Mar 06, 2026, 04:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 27, 2026 Web application page loading issues 1h 36m

Started Jan 27, 2026, 09:20 AM UTC· resolved Jan 27, 2026, 10:56 AM UTC

  1. investigating Jan 27, 2026, 09:20 AM UTC

    We are experiencing problems with the Rollbar Web Application (app.rollbar.com) and page loading. We are looking into this actively and will post when we have identified the issue.

  2. identified Jan 27, 2026, 09:33 AM UTC

    We are currently experiencing service disruptions due to technical issues with one of our third-party upstream providers. This may result in intermittent errors or degraded performance within our platform. Our team is in close contact with the provider, and they have confirmed that a fix is being implemented. We expect services to return to normal shortly. Next Update: As soon as we receive confirmation of the resolution.

  3. identified Jan 27, 2026, 10:09 AM UTC

    Our third-party provider is continuing their efforts to restore full service. We are closely monitoring their progress and will provide further updates as they become available.

  4. resolved 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.

Read the full incident report →

Minor November 20, 2025 Database Maintenance 9h 43m

Started Nov 20, 2025, 04:16 PM UTC· resolved Nov 21, 2025, 01:59 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical October 20, 2025 Service Disruption Across Infrastructure 3h 43m

Started Oct 20, 2025, 07:36 AM UTC· resolved Oct 20, 2025, 11:20 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Notice July 9, 2025 Pipeline processing delays 292d

Started Jul 09, 2025, 04:07 PM UTC· resolved Apr 27, 2026, 04:41 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →