Redis Cloud statusManual checkVerified May 24, 2026Source: status.redis.io
Is Redis Cloud down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from status.redis.io. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Redis Cloud status
Redis Cloud is the hosted Redis offering from Redis Inc. (formerly Redis Labs), covering caching, streams, and the enterprise modules. Incidents are usually scoped to a single subscription in one region, or to one module (RedisSearch, RedisJSON, RedisGraph), rather than affecting every Redis Cloud customer at once.
Components and surfaces that can break
- Surface 01
Managed Redis database endpoints (per region, per subscription).
- Surface 02
Enterprise modules: RedisSearch, RedisJSON, RedisGraph, RedisTimeSeries.
- Surface 03
Redis Cloud Console and the Cluster Management (Pulse) REST API.
Recent Redis Cloud incidents
Redis Cloud maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Redis Cloud is actually down
Check your subscription's region first
Redis Cloud status is per region, per provider (AWS, GCP, Azure). If you run a multi-region active-active (CRDB) subscription, a single-region degradation should be tolerated by your other region â your app needs to reroute traffic, not wait. Single-region subscriptions don't have that fallback, so confirm which region the incident actually hits before changing anything.
Module incidents can hit one command family only
It's common to see RedisSearch (FT.SEARCH) or RedisJSON (JSON.GET) failing while basic GET/SET, INCR, and stream commands keep working. Look at the specific module on the status page; if only one module is degraded, fall back that code path (e.g. skip the search index, read from your primary DB) instead of treating Redis as fully down.
Lean on the pooler and graceful reconnect
A correctly configured Redis client (connection pool, exponential backoff, retry on transient I/O errors) will absorb most short blips. If a 5-15 second incident is surfacing as user-facing 500s, the fix is usually on the client side: enable retries, raise the connect timeout slightly, and don't tear down the pool on the first failure.
Keep firing through the incident
Schedule your own Redis Cloud health check with Crontap
Scheduled cache warmup, scheduled SCAN-based cleanup, and the daily Redis Enterprise metric export via the Pulse REST API are HTTP cron when wrapped in a small endpoint. Crontap fires the endpoint that opens the Redis connection, runs the work, and returns 5xx on failure so the alert surfaces the actual Redis error instead of a generic timeout.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Redis Cloud status: FAQ
- Where can I see the official Redis Cloud status?
- status.redis.io publishes component status for Redis Cloud across regions and providers, plus the enterprise modules and the Cluster Management API. The history page has incident summaries and post-mortems.
- Does Redis Cloud retry queued commands during an incident?
- No. Redis doesn't queue commands server-side on your behalf â once your client's connection drops or times out, the command is gone unless your client retried it. Use a Redis client with built-in retry on transient errors, or wrap critical writes (especially XADD into streams) in your own retry so a brief Redis Cloud blip doesn't lose data.
- What's the difference between Redis Cloud and Redis OSS?
- Redis OSS is the open-source server you self-host. Redis Cloud is the managed, multi-tenant service Redis Inc. runs for you â same Redis protocol and most of the same commands, plus the enterprise modules (RedisSearch, RedisJSON, RedisGraph, RedisTimeSeries), active-active replication, and the Cluster Management API. When status.redis.io shows an incident, it's Redis Cloud (the managed service) that's affected, not OSS Redis you run yourself.