https://approjects-vendor-status-watch.static.hf.space/v/rollbar.htmlIncidents from Rollbar's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000http://status.rollbar.comrollbar:2026-09-16T09:45:01ZWed, 16 Sep 2026 09:45:01 +0000Backlog drained, all processing nominalhttp://status.rollbar.comrollbar:2026-09-01T15:39:45ZTue, 01 Sep 2026 15:39:45 +0000We believe everything is now back to normal , sorry for the inconvenience caused. http://status.rollbar.comrollbar:2026-06-25T15:15:11ZThu, 25 Jun 2026 15:15:11 +0000Incident resolvedhttp://status.rollbar.comrollbar:2026-05-18T20:50:33ZMon, 18 May 2026 20:50:33 +0000We have fully rolled this back and applied the updated image. http://status.rollbar.comrollbar:2026-05-09T19:35:31ZSat, 09 May 2026 19:35:31 +0000Earlier 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 http://status.rollbar.comrollbar:2026-04-20T17:51:35ZMon, 20 Apr 2026 17:51:35 +0000Pipeline processing is back to normal levels for all occurrence variants. This incident has been resolved.http://status.rollbar.comrollbar:2026-04-08T03:59:09ZWed, 08 Apr 2026 03:59:09 +0000This 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: 30s - 37.2 minutes latency 09:02AM - 09:52AM PDT: 30s - 23.1 minutes latency p50 stayed at SLO (~5s) during the entire time period, and no data was lost. The initial cause analysis is a particular traffic pattern. We're investigating the root cause to ensure the system is resilient to this traffic pattern going forward.http://status.rollbar.comrollbar:2026-03-06T15:59:40ZFri, 06 Mar 2026 15:59:40 +0000This incident has been resolved.http://status.rollbar.comrollbar:2026-01-27T09:20:21ZTue, 27 Jan 2026 09:20:21 +0000Our 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.http://status.rollbar.comrollbar:2025-11-20T16:16:04ZThu, 20 Nov 2025 16:16:04 +0000The 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. http://status.rollbar.comrollbar:2025-11-18T11:51:08ZTue, 18 Nov 2025 11:51:08 +0000Incident resolved. Cloudflare applied a patch and all loosk working ok again.http://status.rollbar.comrollbar:2025-10-20T18:36:46ZMon, 20 Oct 2025 18:36:46 +0000Our services have returned to normal operation. Sorry for any inconvenience caused. http://status.rollbar.comrollbar:2025-10-20T07:36:49ZMon, 20 Oct 2025 07:36:49 +0000Our cloud provider has fixed the networking issues they were experiencing.http://status.rollbar.comrollbar:2025-09-03T16:53:23ZWed, 03 Sep 2025 16:53:23 +0000**# 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 exhausted the resources available to other traffic. The range of 502 errors ranged from 30% to 60% of requests during the incident. Once the root cause was identified and mitigated, error levels returned to below 0.01%. The Web App and Processing tiers were not affected. [1] POST requests to api.rollbar.com/api/1/item , api.rollbar.com/api/1/item_batch/ , api.rollbar.com/api/1/items/  **## Follow-Up Actions** We've identified follow-up actions to mitigate going forward 1) the length of similar incidents (completed), 2) the possibility of similar incidents (planned).