Live  /  Providers  /  Redis

Redis

redis.ioNo open incidents

Independent assessment — SquidGrid is not affiliated with Redis. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Cloud & hosting · SquidGrid tracks Redis’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Redis is reporting

Current & recent incidents

Resolved

Redis Cloud – Temporary Issues with Redis IRIS

Minor impact · 2026-09-05 12:58 UTC

Resolved

GCP US-Central1 issue

Minor impact · 2026-09-01 16:00 UTC

Resolved

Regional Network Issues

Minor impact · 2026-07-17 02:02 UTC

Resolved

Connectivity issue on C293

Minor impact · 2026-07-15 22:33 UTC

Resolved

Redis Cloud – Temporary Connectivity Issues to Admin Console

None impact · 2026-06-28 08:52 UTC

Resolved

Instance Failure with endpoint: c270

Minor impact · 2026-06-16 18:38 UTC

Resolved

LangCache Endpoint Issues in GCP us-east4 Region

Minor impact · 2026-06-07 13:08 UTC

Resolved

Redis Cloud – Periodic Maintenance for the Admin Console

Minor impact · 2026-06-07 09:39 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Redis has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Redis runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Redis is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Redis.