outages.live
Live

Rollbar

Rollbar is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

26 min

Longest incident

1 h 13 min

Components

12
Web Application (app.rollbar.com) Operational
90 days agoNo incidentsToday
Homepage (rollbar.com) Operational
90 days agoNo incidentsToday
API Tier (api.rollbar.com) Operational
90 days agoNo incidentsToday
Core Processing Pipeline Operational
90 days agoNo incidentsToday
iOS Symbolication processing pipeline Operational
90 days agoNo incidentsToday
Source map processing pipeline Operational
90 days agoNo incidentsToday
Proguard processing pipeline Operational
90 days agoNo incidentsToday
Mailgun SMTP Operational
90 days agoNo incidentsToday
Mailgun Outbound Delivery Operational
90 days agoNo incidentsToday
rollbar.min.js Operational
90 days agoNo incidentsToday
SCIM and SSO Operational
90 days agoNo incidentsToday
Rollbar Docs Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration13 min11:19 to 11:31Increased occurrence processing pipeline latencyDegraded

Incident resolved.

Sep 16, 2026

Duration26 min09:45 to 10:11Increased occurrence processing pipeline latencyDegraded

Backlog drained, all processing nominal

Sep 1, 2026

Duration1 h 13 min15:39 to 16:53Widespread incident impacting multiple parts of our platform caused by an incident within our cloud providerDegraded

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane