rewindex

CompaniesRedisIncidents

Redis: Connectivity issue on c278

MinorStatus: resolvedStarted Resolved (3.0 h)6 updatesstatus.redis.io (opens in new tab)

Timeline of updates

  1. resolved

    We are currently investigating connectivity issues with some resources that have the following pattern in their endpoint: c278. Some resources in this cluster may be impacted. We will continue to update until the resolution.

  2. resolved

    We have identified the issue and are currently working on the resolution steps. Thank you for your patience.

  3. resolved

    Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.

  4. resolved

    Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.

  5. resolved

    Our teams continue to focus on the resolution steps to fully resolve this issue. Thank you for your continued patience.

  6. resolved

    The incident has been resolved. We will continue to monitor system performance to ensure ongoing stability. If you continue to experience any issues, please contact our support team for assistance.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.redis.io (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Redis, started 2026-05-18 16:52 UTC, resolved after 3.0 h, 6 update(s).

Title
Connectivity issue on c278
Vendor
Redis
Date
URL
https://rewindex.com/company/redis/incidents/510d92ea-5c96-4c68-87d5-16975e2316c6

Redis profileRecent Redis incidentsAll outages on May 18, 2026Redis in May 2026MarkdownJSON