Live

Incident: Reviews might be impacted

0

CodeRabbit reviews might not work correctly in the Reviews component. CodeRabbit reports that this incident is resolved, and it lasted 7 minutes.

State

Resolved

Started

Lasted

7 min

Worst impact

Partial outage

Timeline

2 updates
11:5311:5411:5611:5812:00
Partial outageUpdate postedTimes in UTC

Investigating

7 min 100%

Updates

Times in UTC

As posted by CodeRabbit

Resolved
Investigating

Affected components

1
Reviews

CodeRabbit in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

7 min

This incident

About the median

Follow CodeRabbit

Your coding agent knows when CodeRabbit is down, and tells you when a failure is theirs, not yours. You can also get CodeRabbit 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 "coderabbit" and tell me if CodeRabbit 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=coderabbit
Slack
/feed subscribe https://outages.live/feed.xml?providers=coderabbit

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane