Redis Cloud
Redis Cloud is operational
Checked 14 s ago Operational
History
90 days agoToday
Incidents in 90 days
3
Days with an incident
3
Median duration
3 h 31 min
Longest incident
10 h 36 min
Components
7Admin Console Operational
90 days agoNo incidentsToday
Heroku Integration Operational
90 days agoNo incidentsToday
REST API Operational
90 days agoNo incidentsToday
Support Site Operational
90 days agoNo incidentsToday
DNS Resolvers Operational
90 days agoNo incidentsToday
LangCache Operational
90 days agoNo incidentsToday
Redis Radar Operational
90 days agoNo incidentsToday
Follow Redis Cloud
Your coding agent knows when Redis Cloud is down, and tells you when a failure is theirs, not yours. You can also get Redis Cloud 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 "redis" and tell me if Redis Cloud 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=redisSlack
/feed subscribe https://outages.cc/feed.xml?providers=redisGo from tracking outages to fixing production issues with Polylane.
Try Polylane