Item Processing impact for RUBY and PHY SDKs

What to do

• Check whether your product depends on Rollbar. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-05-09 19:35 UTC and 2026-05-08 21:30 UTC may need a replay.

• Subscribe to Rollbar's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=rollbar works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Rollbar 1

1. resolvedMay 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 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.