Increased processing pipeline latency

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-04-08 03:59 UTC and 2026-04-07 16:52 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 2

1. investigatingApr 7, 2026, 9:02 AM UTC

   Rollbar processing pipeline latency (measured at p99) was elevated above our 30-second p99 SLO today beginning at 02:02AM PDT.

   provider

2. resolvedApr 7, 2026, 4:52 PM UTC

   This 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.

   provider

Corrections

None so far.

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