outages.live
Live
Redis CloudIncident · 2026-09-05 12:58 UTC

Redis Cloud – Temporary Issues with Redis IRIS

ResolvedOfficial update

This issue is now resolved, if you see or experience any additional issues, please contact https://redis.io/support/

The latest update from Redis Cloud.

State

Resolved

Started

57 d ago

2026-09-05 12:58 UTC

Lasted

41 min

until 2026-09-05 13:39 UTC

Worst impact

Degraded

Timeline

2 updates
12:5813:0813:1913:2913:39
DegradedUpdate postedTimes in UTC

Investigating

41 min 100%

Updates

Times in UTC

As posted by Redis Cloud

Resolved2026-09-05 13:39 UTC

This issue is now resolved, if you see or experience any additional issues, please contact https://redis.io/support/

Investigating2026-09-05 13:00 UTC

We’re currently investigating an issue affecting Redis IRIS functionality. Our team is actively working to restore normal service. We’ll provide another update as soon as more information is available.

Redis Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

3 h 31 min

This incident

80% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

10 h 36 min
median 3 h 31 min
90 days agoToday

Other Redis Cloud incidents

All incidents

Redis Cloud·GCP region europe-west2 and zone europe-west2-b issues

All environments have been returned to a full operational state at this time. Please contact our Support team if there are questions or assistance is needed.

Resolvedresolved 12 d ago

Redis Cloud·GCP US-Central1 issue

GCP has confirmed that the US-Central1 event is resolved. Our services are operating normally, and we are marking this issue as closed. If you have any questions or need assistance, please contact support@redis.com.

Resolvedresolved 61 d ago

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=redis
Slack
/feed subscribe https://outages.cc/feed.xml?providers=redis

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane