outages.live
Live
RollbarIncident · 2026-09-01 15:39 UTC

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

ResolvedOfficial update

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

The latest update from Rollbar.

State

Resolved

Started

61 d ago

2026-09-01 15:39 UTC

Lasted

1 h 13 min

until 2026-09-01 16:53 UTC

Worst impact

Degraded

Timeline

3 updates
15:3915:5816:1616:3416:53
DegradedUpdate postedTimes in UTC

Investigating

19 min 26%

Monitoring

54 min 74%

Updates

Times in UTC

As posted by Rollbar

Resolved2026-09-01 16:53 UTC

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

Monitoring2026-09-01 15:59 UTC

It appears that work has been done by our cloud provider which has resolved many of the issues we were experiencing but we will give this some more time while we monitor before resolving this issue.

Investigating2026-09-01 15:39 UTC

We are currently experiencing an incident that is impacting multiple parts of the platform , we believe this is caused by an incident within our cloud provider. We are currently processing data but we are seeing some of our services such as WEB/API are potentially impacted. We will provide an update as we learn more about this issue, and we apologize for any inconvenience this might be causing.

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

2.8× 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·Increased occurrence processing pipeline latency

Backlog drained, all processing nominal

Resolvedresolved 46 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