Live

Database maintenance.

MaintenanceOfficial update

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 update
15:4215:5316:0516:1616:28
MaintenanceUpdate postedTimes in UTC

Scheduled

46 min 100%

Updates

Times in UTC

As posted by Rollbar

Scheduled

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 history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

26 min

This incident

Not comparable

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

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.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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane