Restrictions on Shared Traffic Packages

• Each region can support a maximum of 20 effective traffic packages, without distinguishing between full-time traffic packages and off-peak traffic packages.
• Shared traffic packages have regional attributes and can only offset the public network traffic generated by EIP under the corresponding regional traffic billing mode.
• Shared traffic packages do not support configuration adjustments and renewals, and non-obsolete traffic packages do not support deletion and refunds.
• When a shared traffic package expires or the traffic is exhausted, the traffic package becomes invalid. Resources of invalid traffic packages support deletion, and there is no refund.
• The remaining traffic of a shared traffic package after expiration will become invalid and cannot be transferred to other traffic packages.