Redis Outage History

43 incidents recorded over the last 365 days, 43 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Redis status100.00% uptime history

Every Recorded Redis Incident

Redis incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026GCP region europe-west2 and zone europe-west2-b issues10h 35mResolved
Sep 5, 2026Redis Cloud – Temporary Issues with Redis IRIS41 minResolved
Sep 1, 2026GCP US-Central1 issue3h 30mResolved
Jul 17, 2026Regional Network Issues9h 54mResolved
Jul 15, 2026Connectivity issue on C2934h 58mResolved
Jun 28, 2026Redis Cloud – Temporary Connectivity Issues to Admin Console17 minResolved
Jun 16, 2026Instance Failure with endpoint: c27035 minResolved
Jun 7, 2026LangCache Endpoint Issues in GCP us-east4 Region55h 54mResolved
Jun 7, 2026Redis Cloud – Periodic Maintenance for the Admin Console3h 20mResolved
Jun 3, 2026Network Issues3 minResolved
May 31, 2026Scheduled Maintenance15 minResolved
May 30, 2026Network Issues5 minResolved
May 28, 2026c282 Network Issues14 minResolved
May 27, 2026Scheduled Maintenance3h 32mResolved
May 26, 2026Scheduled Maintenance1h 10mResolved
May 25, 2026Scheduled Maintenance50 minResolved
May 18, 2026Connectivity issue on c2782h 56mResolved
May 17, 2026Scheduled Maintenance16 minResolved
May 13, 2026Connectivity issue on c265.2h 58mResolved
May 10, 2026Clusters – Instance Failure4h 48mResolved
May 8, 2026Network Issues in AWS US-EAST-140h 18mResolved
May 3, 2026Redis Cloud - Periodic maintenance for the admin console551h 57mResolved
Apr 30, 2026Connectivity issues with endpoint c2802h 46mResolved
Apr 28, 2026Connectivity issues with endpoint c556h 4mResolved
Apr 9, 2026Network Issues12 minResolved
Apr 1, 2026Redis Cloud - Temporary connectivity issues to Admin console4h 48mResolved
Apr 1, 2026Network Issues6 minResolved
Mar 26, 2026Network Issues1 minResolved
Mar 22, 2026Redis Cloud - Periodic maintenance for the admin console12 minResolved
Mar 19, 2026Instance failure13 minResolved
Mar 17, 2026Urgent maintenance30 minResolved
Mar 16, 2026Urgent maintenance19 minResolved
Mar 16, 2026Urgent maintenance1h 8mResolved
Mar 16, 2026Urgent maintenance1h 20mResolved
Mar 16, 2026Urgent maintenance1h 16mResolved
Mar 13, 2026Urgent maintenance9 minResolved
Mar 13, 2026Upcoming status page platform transition - Reminder0 minResolved
Mar 12, 2026Urgent maintenance33 minResolved
Mar 10, 2026Urgent maintenance29 minResolved
Mar 10, 2026Instance failure8 minResolved
Mar 8, 2026Redis Cloud - Periodic maintenance for the admin console14 minResolved
Mar 6, 2026Urgent maintenance3h 6mResolved
Mar 3, 2026Urgent maintenance1h 8mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Redis incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Redis Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Redis acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Redis outage in this window ran 22d 23h, against a mean recovery of 16h 50m. If you depend on Redis in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.