Increased occurrence processing pipeline latency
ResolvedOfficial update
Incident resolved.
The latest update from Rollbar.
State
Resolved
Started
5 d ago
2026-10-28 11:19 UTC
Lasted
13 min
until 2026-10-28 11:31 UTC
Worst impact
Degraded
Timeline
2 updates11:1911:2211:2511:2811:31
DegradedUpdate postedTimes in UTC
Identified
13 min 100%
Updates
Times in UTCAs posted by Rollbar
Resolved2026-10-28 11:31 UTC
Incident resolved.
Identified2026-10-28 11:19 UTC
We are experiencing a processing delay in our occurrence pipeline. We are investigating actively and will post when we have identified the issue.
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=rollbarSlack
/feed subscribe https://outages.cc/feed.xml?providers=rollbarFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane