Rewindex

CompaniesRollbarIncidents

Rollbar: Increased occurrence processing pipeline latency

MinorStatus: resolvedStarted Resolved (26 min)4 updatesstatus.rollbar.com (opens in new tab)
Part of an outage event

Salesforce outage, Sep 16, 2026 · 16 vendors, 21 incidents

Rollbar’s incident started in the same window without naming Salesforce (timing only, not evidence of a link). (timing only, posted +2 h 26 min vs Salesforce’s own post)

Swipe sideways to see the whole diagram.

same windowSalesforceposted 07:19 UTC1 to 4 hours later4 vendors, 4 blamed SalesforceBraze, Gong, ClickHouse Cloud, SmartsheetLater1 vendor, 1 blamed SalesforceSalesloftRollbar (this incident)posted +2 h 26 min
same windowSalesforceposted 07:19 UTC1 to 4 hours later4 vendors, 4 blamed SalesforceBraze, Gong, ClickHouseCloud, SmartsheetLater1 vendor, 1 blamed SalesforceSalesloftRollbar (this incident)posted +2 h 26 min
Rollbar is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Salesforce<br/>posted 07:19 UTC"]:::root
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Salesforce<br/>Braze, Gong, ClickHouse Cloud, Smartsheet"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed Salesforce<br/>Salesloft"]:::blames
  root --> later
  me["Rollbar (this incident)<br/>posted +2 h 26 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Core Processing PipelineiOS Symbolication processing pipelineSource map processing pipelineProguard processing pipeline

Timeline of updates

  1. investigating

    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

    Root cause identified. Fix applied.

  3. monitoring

    Processing backlog. Issue solved.

  4. resolved

    Backlog drained, all processing nominal

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.rollbar.com (opens in new tab).

Rollbar profileRecent Rollbar incidentsMarkdownJSON