outages.live
Live
RollbarIncident · 2026-09-16 09:45 UTC

Increased occurrence processing pipeline latency

ResolvedOfficial update

Backlog drained, all processing nominal

The latest update from Rollbar.

State

Resolved

Started

46 d ago

2026-09-16 09:45 UTC

Lasted

26 min

until 2026-09-16 10:11 UTC

Worst impact

Degraded

Timeline

4 updates
09:4509:5109:5810:0410:11
DegradedUpdate postedTimes in UTC

Investigating

4 min 14%

Identified

14 min 52%

Monitoring

9 min 33%

Updates

Times in UTC

As posted by Rollbar

Resolved2026-09-16 10:11 UTC

Backlog drained, all processing nominal

Monitoring2026-09-16 10:02 UTC

Processing backlog. Issue solved.

Identified2026-09-16 09:48 UTC

Root cause identified. Fix applied.

Investigating2026-09-16 09:45 UTC

We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.

Rollbar in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

26 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

1 h 13 min
median 26 min
90 days agoToday

Other Rollbar incidents

All incidents

Rollbar·Increased occurrence processing pipeline latency

Incident resolved.

Resolvedresolved 4 d ago

Rollbar·Widespread incident impacting multiple parts of our platform caused by an incident within our cloud provider

We believe everything is now back to normal , sorry for the inconvenience caused.

Resolvedresolved 61 d ago

Follow Rollbar

Your coding agent knows when Rollbar is down, and tells you when a failure is theirs, not yours. You can also get Rollbar incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "rollbar" and tell me if Rollbar has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=rollbar
Slack
/feed subscribe https://outages.cc/feed.xml?providers=rollbar

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane