- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 44of 100
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 8h 6m it lasted.
Anything that failed between 2025-10-20 18:36 UTC and 2025-10-21 02:43 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 9
- identified
We are experiencing a processing delay in our occurrence pipeline. We believe this is due to the ongoing issues with AWS that impact some of the other external services we use across our applications. We apologize for any inconvenience caused by this and will endeavor to do what we can to resolve this.
provider
- identified
We are now experiencing impact to other parts of the pipeline including the API, this again we believe is still connected to the ongoing incident with AWS which has impacted other external services.
provider
- identified
We are working on mitigations that will get around some of the externally degraded services.
provider
- monitoring
We are continuing to apply some mitigations but with the current work we can now see that our API is stable , we are just processing a backlog of other messaging that will be delayed in completing due to the volume. I will leave our pipeline as degraded while that is processing and we will move this to a monitoring phase. Sorry for the inconvenience.
provider
- monitoring
We have identified that some people are experiencing issues with the WEB Frontend this is also connected to the AWS impacts we are looking at how to mitigate this.
provider
- monitoring
We are still experiencing the effects of the AWS outage through some of our 3rd party services, we are continuing to investigate and apply mitigations around this whilst also ensuring that we maintain consistent and secure processes. Apologies for this inconvenience, we will continue to provide updates during this time.
provider
- monitoring
Due to ongoing issues with some of the services we have applied additional changes to our applications, our pipeline is processing as normal but there may still be some lingering effects with the WEB interface. However we have continued to process and store data we have received , all of our clients should have received the notifications defined in their accounts with the understanding that services such as SLACK/MAILGUN and other notification applications may also have been impeded during this time. We are continuing to address the issues as they arise but believe that we are progressing to the end point that satisfies all of our customers.
provider
- monitoring
At present everything appears to have recovered , we will leave this in a monitoring phase for the next 30 mins.
provider
- resolved
Our services have returned to normal operation. Sorry for any inconvenience caused.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-391cd059e7
Is Rollbar still down?
No, this incident was resolved 2025-10-21 02:43 UTC. For Rollbar's live state, see https://down.guide/rollbar.
How long did it last?
8h 6m, from 2025-10-20 18:36 UTC to 2025-10-21 02:43 UTC, by the times Rollbar posted.
What caused it?
Rollbar hasn't published a root cause. If it does, it shows here.
Where does this come from?
Rollbar's official status page, https://status.rollbar.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.