All Products
Search
Document Center

Tair (Redis® OSS-Compatible):Retired instance types

Last Updated:Mar 28, 2026

These Tair (Redis OSS-compatible) specifications are no longer available for purchase. Existing instances continue to work normally. This page lists the connection limits, bandwidth, and queries per second (QPS) reference values for each retired specification.

Standard Edition for zone-disaster recovery

SpecificationInstanceClass (for API calls)Maximum connectionsBandwidth (MB/s)QPS reference
1 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb1g.1db.0rodb.4proxy.default10,0001080,000
2 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb2g.1db.0rodb.4proxy.default10,0001680,000
4 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb4g.1db.0rodb.4proxy.default10,0002480,000
8 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb8g.1db.0rodb.4proxy.default10,0002480,000
16 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb16g.1db.0rodb.4proxy.default10,0003280,000
32 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb32g.1db.0rodb.4proxy.default10,0003280,000
64 GB zone-disaster recovery instanceredis.logic.sharding.drredissdb64g.1db.0rodb.4proxy.default10,0004880,000

Cluster Edition (dual-replica)

SpecificationInstanceClass (for API calls)ShardsMaximum connectionsBandwidth (MB/s)QPS reference
1 GB cluster instance (2 shards)redis.logic.sharding.512m.2db.0rodb.4proxy.default220,00048200,000
1 GB cluster instance (4 shards)redis.logic.sharding.256m.4db.0rodb.4proxy.default440,00096400,000
2 GB cluster instance (4 shards)redis.logic.sharding.512m.4db.0rodb.4proxy.default440,00096400,000
2 GB cluster instance (8 shards)redis.logic.sharding.256m.8db.0rodb.8proxy.default880,000192800,000
4 GB cluster instance (8 shards)redis.logic.sharding.512m.8db.0rodb.8proxy.default880,000192800,000
4 GB cluster instance (16 shards)redis.logic.sharding.256m.16db.0rodb.16proxy.default16160,0003841,600,000
8 GB cluster instance (16 shards)redis.logic.sharding.512m.16db.0rodb.16proxy.default16160,0003841,600,000
8 GB cluster instance (32 shards)redis.logic.sharding.256m.32db.0rodb.32proxy.default32320,0007683,200,000
16 GB cluster instance (32 shards)redis.logic.sharding.512m.32db.0rodb.32proxy.default32320,0007683,200,000
16 GB cluster instanceredis.sharding.small.default880,000768640,000
32 GB cluster instanceredis.sharding.mid.default880,000768640,000
64 GB cluster instanceredis.sharding.large.default880,000768640,000
128 GB cluster instanceredis.sharding.2xlarge.default16160,0001,5361,280,000
256 GB cluster instanceredis.sharding.4xlarge.default16160,0001,5361,280,000
512 GB cluster instanceredis.sharding.8xlarge.default32320,0002,0482,560,000

Cluster Edition for zone-disaster recovery

SpecificationInstanceClass (for API calls)ShardsMaximum connectionsBandwidth (MB/s)QPS reference
16 GB cluster instance for zone-disaster recoveryredis.logic.sharding.drredismdb16g.8db.0rodb.8proxy.default880,000768640,000
256 GB cluster instance for zone-disaster recoveryredis.logic.sharding.drredismdb256g.16db.0rodb.16proxy.default16160,0001,5361,280,000
512 GB cluster instance for zone-disaster recoveryredis.logic.sharding.drredismdb512g.32db.0rodb.32proxy.default32320,0002,0482,560,000

Bandwidth calculation rules

Each bandwidth value in the tables above represents the total bandwidth for the entire instance — the combined bandwidth across all shards or nodes.

Bandwidth applies equally to upstream and downstream traffic. For example, a 10 MB/s (80 Mbps) instance has 10 MB/s upstream and 10 MB/s downstream.

The bandwidth limits of Tair and Redis Open-Source Edition refer to the data transfer capacity of individual shards within their respective distributed systems. The limits are generally independent of the network connection type used by clients.

To handle unexpected or scheduled traffic peaks, adjust the instance bandwidth. For details, see Manually increase the bandwidth of an instance.

For common bandwidth questions, see FAQ about bandwidth.

FAQ

The zone-disaster recovery specifications are retired. How do I create an instance with zone-disaster recovery?

The zone-disaster recovery architecture has been upgraded. When creating an instance, set Zone Type to Dual-zone and specify a Primary Zone and a Secondary Zone.