Rollbar experienced a minor incident on May 8, 2026 affecting Core Processing Pipeline and iOS Symbolication processing pipeline and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved May 08, 2026, 09:30 PM UTC
Status: Resolved 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. Affected components Source map processing pipeline (Operational) Proguard processing pipeline (Operational) Homepage (rollbar.com) (Operational) Web Application (app.rollbar.com) (Operational) SCIM and SSO (Operational) iOS Symbolication processing pipeline (Operational) Mailgun Outbound Delivery (Operational) API Tier (api.rollbar.com) (Operational) Mailgun SMTP (Operational) Core Processing Pipeline (Operational) Rollbar Docs (Operational) rollbar.min.js (Operational)