Knowledge

English

简体中文
日本語

English

简体中文
日本語

Appearance

Network accounting and protection ​

1. Guarantee and starting strategy ​

  1. “0M guarantee” is only applicable to new users’ first-month experience.
  2. Starting from the second month, the minimum guarantee is: -International ordinary network: 500M.
  • International optimization/continental optimization network (such as IIJ, BBTEC): 100M.

2. Bandwidth billing rules ​

  1. Both guaranteed and burst bandwidth are billed at the 95th Percentile.
  2. The unit price of burst bandwidth is increased by 0.05 USD/M based on the selected guaranteed unit price.
  3. Example: When the minimum guarantee is 0.20 USD/M, the unit price of the burst part is 0.25 USD/M.

3. DDoS protection rules ​

  1. Provide 2 free DDoS protection events every calendar month.
  2. The billing cycle for a single protection is 3 days, and any period less than 3 days will be counted as 3 days.
  3. Protection capabilities are limited by current network capacity and upstream capabilities.
  4. Bandwidth during DDoS is calculated according to the regular 95th billing rule.
  5. During non-DDoS periods, bandwidth is billed according to the larger value in the inbound and outbound directions.
  6. When the free times are exceeded or high-defense services need to be continued, billing will be based on 0.6 USD/M, based on the actual peak traffic after cleaning.

4. Network stability and resolution ​

  1. When the scale of the attack exceeds the current protection capabilities, we will not be liable for any resulting business interruption.
  2. If the attack seriously affects the backbone network or other customers, we have the right to temporarily blackhole the attacked IP.

5. Line level description ​

  1. International Standard
  2. International Optimized
  3. Mainland China Optimized (such as IIJ, BBTEC)
  4. Premium Mainland China Optimized (such as CN2 GIA, CUVIP/AS9929, CMI)

6. Routing and Advertisement Compliance ​

  1. Before customers make BGP announcements, routing policy changes, or ASN-related configurations, they should confirm feasibility and compliance with us in advance.
  2. The responsible party shall bear the upstream penalties and business impact caused by incorrect route announcements, hijacking, leaks, or policy mismatches.