G-core Lab CDN Network Situation Analysis Brief

Original link: https://www.blueskyxn.com/202208/6420.html

G-core Lab CDN 网络情况分析简报

foreword

The main content has been introduced in the old article G-core Lab CDN: Free 1T per month + support for PayPal, UnionPay, etc. + custom SSL + support for WS + support for CNAME access .

This article focuses on re-analysis of its CDN network performance in mainland China

The IP reference list is supplemented at the end of the text

Bandwidth Performance Test of China Telecom’s Home Broadband Environment

The source site is a 400M server in West America, and the test environment is about the same bandwidth.

The test environment has been tested at the same time, and reached the following level when using the CN2 GIA network

  1. ping 167
  2. Google ping 865
  3. AvgSpeed ​​20.49MB
  4. MaxSpeed ​​31.52MB

The test environment has been tested over the same period and reached the following levels when using the CloudFlare CDN self-selected IP network

  1. ping 179
  2. Google ping 980
  3. AvgSpeed ​​13.29MB
  4. MaxSpeed ​​19.01MB

We grabbed 5 time periods on Friday and Saturday for testing

gcorecdn-20220820.jpg

The redder the color, the faster the speed, the greener the color, the slower the speed (here refers to the bandwidth)

It can be seen that the speed of China Telecom Home Broadband is strong during the morning of Beijing time, and it drops significantly in the afternoon and evening.

Among them, IPs worth commenting are:

① 92.38.145.145 United States (North American broadcast)

Using the network connection of China Telecom’s backbone network (China-Los Angeles, USA) US TATA, since it is directly connected to the United States, and the server is located in the United States, the performance of Telecom China and the United States is still acceptable, so it is obvious that compared with other IPs, Google ping (refer to back Source traffic) has obvious advantages, ping (referring to non-return-to-source traffic) is in the United States, so its performance is average, and the all-day bandwidth performance is relatively good compared to other IPs. Generally, except at night, it has a level of 5~20MB/s. In this case, it can beat the speed performance of CloudFlare CDN US.

②5.252.26.62 [IPIPnet says Bangkok, Thailand]

Using the China Telecom backbone network (China-Singapore)-NTT (Singapore-Malaysia-Thailand) network connection, this route has a geographical advantage, and China Telecom-Singapore does have a good speed under some direct connection conditions (for example, the same circumstance). Dubai Oracle in Singapore) also performs better in latency due to its close geographical location.

③5.101.222.14 [IPIPnet says Toronto, Canada]

The performance of this IP is the same as that of the United States in most cases, which is a more stable choice

④92.223.78.30 [IPIPnet says Sydney, Australia], 92.223.92.30 [IPIPnet says Warsaw, Poland], 92.223.112.62 [IPIPnet says Luxembourg], 80.240.113.62 [IPIPnet says Stockholm, Sweden], 93.123.11.62 [IPIPnet says say London, England]

The best bandwidth performance of these IPs is okay, but it seems that there may be big differences at different times, which can be tested according to the actual situation

ITDOG HTTPS GET Test

The test uses 3 tests, and the 3rd time is taken. The test objects are mainly the above, and only the nodes in mainland China are tested.

  1. 92.38.145.145 United States (North American broadcast): The national average is 1.381s, and the three major operators are similar
  2. 5.252.26.62 [IPIPnet says Bangkok, Thailand]: The national average is 0.953s, the telecom is slightly higher, and China Unicom Mobile 0.7s
  3. 5.101.222.14 [IPIPnet says Toronto, Canada]: The national average is 2.127s, and the movement is slightly faster
  4. 92.223.78.30 [IPIPnet says Sydney, Australia]: The national average is 1.762s, and the mobile is fast to 0.922s
  5. 92.223.92.30 [IPIPnet says Warsaw, Poland]: The national average is 1.904s, and the mobile is fast to 1.293s
  6. 92.223.112.62 [IPIPnet says it is Luxembourg]: The national average is 1.488s, telecom is slower, China Unicom is faster, and mobile is a little faster
  7. 80.240.113.62 [IPIPnet says Stockholm, Sweden]: The national average is 1.853s, telecom is slower, China Unicom is faster, and mobile is faster
  8. 93.123.11.62 [IPIPnet says it is London, UK]: The national average is 1.768s, China Unicom is slower, mobile is faster
  9. 92.223.95.95 Japan [IPIPnet says it is Asia-Pacific broadcast]: The national average is 2.070s, the mobile is as fast as 0.728s, China Unicom is slow, and telecom is even slower
  10. 92.223.63.254 Japan: The national average is 2.522s, China Unicom is as fast as 1.463s, and telecom is slower
  11. 92.223.76.254 Hong Kong: The national average is 2.547s, China Unicom is slow, Telecom is slower, and mobile is as fast as 0.999s
  12. 92.223.116.254 Singapore: National average 2.278s, moving fast to 0.518s
  13. 120.28.10.46 [IPIPnet says Manila, Philippines]: The national average is 1.701s, the telecom is slower, and the mobile is 1.150s
  14. 92.223.74.254 [IPIPnet says Prague, Czech Republic]: National average 1.926s, Unicom 1.063s, Mobile 1.396s
  15. 92.223.124.254 [IPIPnet says it is European pancasting]: National average 1.562s, Telecom 1.777s, China Unicom 1.135s, Mobile 1.472s
  16. 103.1.211.14 [IPIPnet says Ho Chi Minh, Vietnam]: Unicom 0.759s, others are very slow

control group

  1. CloudFlare’s self-selected IP (screened a few days ago, 172.66.42.172 was randomly selected, and the others were brought down by GFW): National average 1.994s, Telecom 1.853s, China Unicom 1.170s, Mobile 3.988s
  2. Beijing Jinshan Cloud 110.43.204.172 participating in the anti-generation CF: the national average of 0.457s
  3. Guangzhou Mobile participating in the anti-generation CF 120.232.150.100: the national average of 0.716s
  4. Yinchuan Mobile who participated in the anti-generation CF 111.51.67.188: the national average of 0.628s
  5. Hong Kong HUAWEI CLOUD participating in the anti-generation CF 159.138.130.126: National average 0.573s
  6. Hong Kong zenlayer23.91.98.239 participating in the anti-generation CF: the national average is 1.746s
  7. Hong Kong Tencent Cloud participating in the anti-generation CF 43.128.1.112: National average 1.036s
  8. Singapore Tencent Cloud: National average 0.905s
  9. Bricklayer DC6 CN2 GIA: National average 0.806s
  10. Baidu Cloud Acceleration (Chongqing Mobile): National average 0.426s
  11. Baidu Cloud Acceleration (Liaoning Unicom): National average 0.460s
  12. Baidu Cloud Acceleration (Guangdong Telecom): National average 0.470s
  13. DogeCloud CDN (National Load): National Average 0.385s
  14. Oracle Dubai: National average of 1.602s
  15. Contabo, USA: National average of 1.725s

It can be seen that some nodes perform well in some network conditions, such as Thai IP, etc., and ordinary nodes can basically connect directly to CloudFlare. At the same time, due to the recent large-scale interference of CloudFlare in mainland China, it is randomly blocked. Mainland users have poor performance when accessing CloudFlareCDN. At this time, they can consider using G-Core CDN, self-built CDN and AWS CloudFront

It is equivalent to AWS that the billing is unclear and difficult to register. The registration of G-Core is simpler and the billing is capped.

G-core CDN IP Reference List

For reference only, may not be complete, theoretically claims to have 140+ nodes

  • 81.28.12.12 Global broadcast (America/Singapore/Hong Kong/Japan/Germany/France/Italy/UK/Russia-Moscow/Bangladesh/South Africa/Brazil, etc., may not include Korea/UAE/Australia/Switzerland/India/China Mainland/Taiwan, because the routing is not very smart, the same IPs such as Hong Kong, Singapore, the United States, some local access and some around 108,000 miles)
  • 92.223.84.84 looks like global anycast as above
  • 92.223.95.95 Japan [IPIPnet says it is Asia-Pacific pancasting]
  • 92.223.63.254 Japan
  • 92.38.145.145 USA (North America Pancast)
  • 92.223.126.62 Netherlands [IPIPnet says Amsterdam, Netherlands]
  • 92.223.116.254 Singapore
  • 92.223.76.254 Hong Kong
  • 92.223.97.97 European Pancast (eu.a.gcdn.co)
  • 92.223.124.254 [IPIPnet says it is European pancasting]
  • 93.123.11.62 [IPIPnet says London, UK]
  • 120.28.10.46 [IPIPnet says Manila, Philippines]
  • 92.223.78.30 [IPIPnet says Sydney, Australia]
  • 5.252.26.62 [IPIPnet says Bangkok, Thailand]
  • 81.28.14.14 [IPIPnet says Sao Paulo, Brazil]
  • 94.176.183.62 [IPIPnet says Paris, France]
  • 92.223.74.254 [IPIPnet says Prague, Czech Republic]
  • 92.38.142.30 [IPIPnet says Istanbul, Turkey]
  • 92.223.92.30 [IPIPnet says Warsaw, Poland]
  • 95.85.69.62 [IPIPnet says Bucharest, Romania]
  • 5.188.126.99 [IPIPnet says Madrid, Spain]
  • 5.188.133.99 [IPIPnet says Johannesburg, South Africa]
  • 92.223.55.62 [IPIPnet says Marseille, France]
  • 5.101.222.14 [IPIPnet says Toronto, Canada]
  • 87.120.164.62 [IPIPnet says Buenos Aires, Argentina]
  • 80.240.113.62 [IPIPnet says Stockholm, Sweden]
  • 91.243.87.62 [IPIPnet says Chisinau, Moldova]
  • 45.82.101.62 [IPIPnet says Milan, Italy]
  • 5.188.94.5 [IPIPnet says Tel Aviv, Israel]
  • 92.223.112.62 [IPIPnet says Luxembourg]
  • 150.107.126.62 [IPIPnet says Lagos, Nigeria]
  • 103.1.211.14 [IPIPnet says Ho Chi Minh, Vietnam]
  • 195.14.146.81 [IPIPnet says Cyprus]
  • 87.120.106.62 [IPIPnet says Bogota, Colombia]
  • 45.82.103.62 [IPIPnet says Santiago, Chile]
  • 213.156.151.62 [IPIPnet says Lima, Peru]

This article is reprinted from: https://www.blueskyxn.com/202208/6420.html
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment