Tair (Redis® OSS-Compatible) instances running Redis® Open-Source Edition 4.0 will reach End of Life (EOL) on September 25, 2026 (Singapore Time, UTC+8). Upgrade your instances to a higher version at your earliest convenience to maintain service continuity.
EOL timeline and impact
The EOL process follows three milestones:
Milestone | Date (Singapore Time, UTC+8) | Impact |
End of Sale (EOS) | October 25, 2025 | New purchases of Redis® Open-Source Edition 4.0 instances are no longer available. All development and iteration for this version, including new features and security patches, will cease. |
End of renewal and specification change | March 25, 2026 | Renewals and specification changes for existing Redis® Open-Source Edition 4.0 instances are no longer available. Active services remain operational until the final EOL date. |
End of Life (EOL) | September 25, 2026 | All services for Redis® Open-Source Edition 4.0 instances will be terminated. Access to data, related documentation, and technical support for these instances will be permanently discontinued. |
What happens if you take no action
Redis® Open-Source Edition 4.0 instances will not be automatically upgraded. If you do not upgrade before September 25, 2026, your instances will be shut down. Access to data, related documentation, and technical support will be permanently discontinued.
Back up your instance data before the EOL date. For instructions, see Backup and restoration.
Recommended actions
Upgrade your instances to Redis® Open-Source Edition 5.0 using one of the following methods.
In-place upgrade (recommended)
Perform an in-place upgrade to Redis® Open-Source Edition 5.0. This version offers significant improvements in master-replica replication, data persistence, and overall performance, along with access to new features and full backward compatibility to Redis® Open-Source Edition 4.0.
The upgrade process minimizes downtime:
The system upgrades the replica node first. During this phase, the master node remains fully operational and continues handling read and write requests.
After the replica upgrade completes, a switchover promotes the upgraded replica node to the new master node. Schedule this switchover to occur either immediately or within your configured maintenance window. During the switchover, the instance becomes read-only for up to 60 seconds to ensure complete data synchronization and is temporarily disconnected for a few seconds. Make sure your application can automatically reconnect to the instance.
After the upgrade, your instance ID, endpoints, data, IP whitelist settings, and all existing account credentials remain unchanged.
Clone data to a new instance
If you want to test and validate your application with Redis® Open-Source Edition 5.0 before upgrading production, clone your existing instance to a Redis® Open-Source Edition 5.0 instance. This approach lets you run tests without affecting your production environment.
FAQ
Will my existing Redis® Open-Source Edition 4.0 instances be automatically upgraded?
No. Instances running Redis® Open-Source Edition 4.0 will be shut down after the EOL date (September 25, 2026). There is no automatic upgrade. Upgrade your instances manually before this date.
What commands are supported in later versions of Redis® Open-Source Edition?
Later versions of Redis® Open-Source Edition undergo extensive backward-compatibility testing for data structures and APIs. For details, see Commands supported by Redis® Open-Source Edition.
How do I test for compatibility before upgrading?
Create a pay-as-you-go Redis® Open-Source Edition 5.0 instance and clone your existing instance to it. Run your application tests against the new instance. After testing is complete, delete the new instance to avoid further charges.