Database maintenance.
We'll be performing a scheduled maintenance in our databases. This may result in delays of item processing. Sorry for the inconveniences.
The latest update from Rollbar.
State
Scheduled
Started
Ongoing for
46 min
Worst impact
Maintenance
Timeline
1 updateScheduled
46 min 100%
Updates
Times in UTCAs posted by Rollbar
We'll be performing a scheduled maintenance in our databases. This may result in delays of item processing. Sorry for the inconveniences.
Rollbar in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
26 min
This incident
Not comparable
Other Rollbar incidents
All incidentsRollbar·Increased occurrence processing pipeline latency
Incident resolved.
Rollbar·Increased occurrence processing pipeline latency
Backlog drained, all processing nominal
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.
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.
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.live/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.
https://outages.live/feed.xml?providers=rollbar/feed subscribe https://outages.live/feed.xml?providers=rollbarFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane