Rollbar: Widespread incident impacting multiple parts of our platform caused by an incident within our cloud provider
Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents
Rollbar’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +58 min vs Google Cloud’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
root --> h1
h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
root --> h4
p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
root -.-> p0
k0["Bolt.new<br/>+24 min"]:::hop2
p0 -->|"blamed GitHub"| k0
p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
p1 -->|"blamed Twilio"| k1
me["Rollbar (this incident)<br/>posted +58 min"]:::me
root -.->|"same window"| meFull 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 PipelineRollbar DocsWeb Application (app.rollbar.com)rollbar.min.jsSCIM and SSOiOS Symbolication processing pipelineSource map processing pipelineMailgun Outbound DeliveryAPI Tier (api.rollbar.com)Mailgun SMTPProguard processing pipelineHomepage (rollbar.com)
Timeline of updates
- investigating
We are currently experiencing an incident that is impacting multiple parts of the platform , we believe this is caused by an incident within our cloud provider. We are currently processing data but we are seeing some of our services such as WEB/API are potentially impacted. We will provide an update as we learn more about this issue, and we apologize for any inconvenience this might be causing.
- monitoring
It appears that work has been done by our cloud provider which has resolved many of the issues we were experiencing but we will give this some more time while we monitor before resolving this issue.
- resolved
We believe everything is now back to normal , sorry for the inconvenience caused.
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).