All Products
Search

This Product

    Tair (Redis® OSS-Compatible):Manually increase instance bandwidth

    Document Center

    Tair (Redis® OSS-Compatible):Manually increase instance bandwidth

    Last Updated:Mar 30, 2026

    When your instance approaches its bandwidth limit during traffic spikes — such as flash sales or large key operations — increase the bandwidth directly without changing instance specifications. The adjustment takes effect within about 1 minute and causes no connection interruptions.

    Use cases

    Scenario When to use
    Traffic spikes Promotional events like flash sales drive a sudden surge in requests. Increase bandwidth before the event and decrease it afterward to control costs.
    Large key operations Heavy read/write operations on large keys within a short period saturate bandwidth. Temporarily increase bandwidth to protect service stability.
    Request skew in cluster instances In cluster or read/write splitting instances, specific shards or read replicas are accessed disproportionately while others remain idle. Increase bandwidth for only those shards instead of upgrading the entire instance.
    Standard instance at maximum specifications The instance is already at its highest available specification and the bandwidth still falls short. Increase bandwidth without upgrading to cluster architecture.

    To check whether you need to increase bandwidth, see View monitoring data.

    Limitations

    • Bandwidth can be increased by up to 6× the default bandwidth for the instance type, with a maximum increase of 192 Mbit/s per instance or shard.

      Examples:

      • A 2 GB memory-optimized standard Tair instance has a default bandwidth of 96 Mbit/s. Its bandwidth can be increased by up to 192 Mbit/s, reaching a maximum of 288 Mbit/s.

      • A 256 MB standard Redis Open-Source Edition instance has a default bandwidth of 10 Mbit/s. Its bandwidth can be increased by up to 60 Mbit/s, reaching a maximum of 70 Mbit/s.

      For the default bandwidth of each instance type, see Instance specifications.

    • The following operations invalidate any extra bandwidth you have purchased, and you receive a refund for the unused portion. Re-increase bandwidth after the operation if needed.

      Operation Validity after operation
      Major version upgrade Invalid
      Change configurations — standard architecture Remains valid
      Change configurations — other architectures Invalid
      Change the zone — standard architecture Remains valid
      Change the zone — other architectures Invalid

    • Tair (Enterprise Edition) disk-based instances do not support bandwidth modification.

    Billing

    Extra bandwidth is billed hourly based on the amount purchased and the duration of use. Default bandwidth is free — charges apply only to the extra bandwidth you purchase. Billing rates vary by region. For details, see Billing items.

    Increase the bandwidth

    Prerequisites

    Before you begin, ensure that you have:

    Increase bandwidth manually

    1. Log in to the console and go to the Instances page. In the top navigation bar, select the region where your instance resides. Find the instance and click its ID.

    2. In the Configuration Information section, click Modify next to Bandwidth MB/s.

      The Configuration Information section shows the maximum internal bandwidth of the instance. For cluster or read/write splitting instances, this is the sum of the bandwidths allocated to all data nodes.

    3. In the panel that appears on the right, select the extra bandwidth to purchase:

      • Standard instance: Set the bandwidth for the instance.

      • Cluster or read/write splitting instance: Choose one of the following options:

        • Adjust Bandwidth for All Shards — Increase or decrease bandwidth uniformly across all shards, for example, before a flash sale.

        • Adjust Bandwidth for Individual Shards — Increase or decrease bandwidth for specific shards, for example, to address request skew. Use instance diagnosis to identify which shards have skewed traffic.

      Click OK.

    4. Click Pay and complete the payment.

    After payment, the new maximum bandwidth (existing bandwidth + extra bandwidth) takes effect within about 1 minute.

    Decrease or cancel bandwidth

    To decrease bandwidth or cancel extra bandwidth entirely, follow the same steps. Move the bandwidth slider to the target value — or to the leftmost position to revert to the default bandwidth — then click Pay.

    During off-peak hours, decrease bandwidth to reduce costs. To monitor bandwidth usage, see View monitoring data.

    What's next

    • Automate bandwidth adjustments: Use the bandwidth Auto Scaling feature to increase or decrease bandwidth automatically when usage crosses a threshold — reducing manual intervention and O&M overhead.

    • Schedule bandwidth increases: For Tair instances, schedule bandwidth upgrades ahead of known traffic peaks, such as planned promotions.

    • Upgrade to Tair (Enterprise Edition): If you need a significant bandwidth increase on a Redis Open-Source Edition instance, switch to Tair (Enterprise Edition), where every specification provides 96 Mbit/s or more of bandwidth.

    API reference

    API Description
    EnableAdditionalBandwidth Adjusts the bandwidth of an instance

    FAQ

    Why can't I find the Maximum Bandwidth button?

    Tair (Enterprise Edition) disk-based instances do not support bandwidth modification. The Maximum Bandwidth button is not available for these instance types.

    Why is my maximum bandwidth limited to 3× the default instead of 6×?

    Your instance likely has a subscription bandwidth plan active. Go to My Orders and search for an order with the ID format Instance ID-bw (for example, r-2zew****qs67bqho3n-bw). Unsubscribe from that plan, then purchase a pay-as-you-go bandwidth plan instead. Pay-as-you-go plans allow you to increase bandwidth up to 6× the default.

    Does a bandwidth adjustment cause connection interruptions?

    No. Bandwidth adjustments take effect without any connection interruptions — ready to use immediately after the change applies.

    How do I adjust bandwidth for a specific shard in a cluster instance?

    In step 3 of the procedure, select Adjust Bandwidth for Individual Shards and choose the specific shards to adjust. This is useful for eliminating request skew without increasing bandwidth across the entire instance. Use instance diagnosis to identify which shards have disproportionate traffic.

    How do I cancel extra bandwidth?

    In step 3 of the procedure, move the bandwidth slider to the leftmost position to revert to the default bandwidth for your instance type. Review the estimated cost and complete the payment.

    If I change my instance configurations after purchasing extra bandwidth, am I still charged?

    It depends on the instance architecture:

    • Standard architecture: The extra bandwidth remains valid and you continue to be charged after a configuration change. Your total bandwidth becomes the sum of the new instance type's default bandwidth and the extra bandwidth you purchased.

    • Other architectures (cluster, read/write splitting): The extra bandwidth becomes invalid and you are no longer charged. Re-increase the bandwidth after the configuration change if needed.

    For bandwidth limits per instance type, see .