Gcorelabs CDN – the best alternative to Cloudflare

foreword

The Gcorelabs CDN has had a lot of changes recently, most importantly supporting the websocket feature of HTTP/2, which is very valuable to us. Today we’ll see if Gcorelabs’ CDN is up to the task.

Global Node Distribution

The following IP segments are all scanned by blogger Leo’s self-written scanning software on BGP.TOOLS to obtain the full IP segment of Gcorelabs ASN, which should be the most complete Gcorelabs CDN IP segment arrangement on the entire network. This article is based on the CC BY-NC-SA 4.0 agreement, which is allowed to be reproduced, but the original author’s name and article address must be retained.

Gcorelabs’ CDN business has a large number of nodes around the world. Although it is not as many as Cloudflare in the end, it is not ambiguous in the area it covers. In the Asia-Pacific region, their CDN nodes are in Singapore (featured), Hong Kong, Seoul, Boli (featured), and Tokyo.

Singapore

CDN IP segment: 92.223.116.0/24
Actual IPs available for CDN: 92.223.116.200-216, 92.223.116.254

Singapore Gcorelabs bought the Transit of Singapore Mobile CMI, so the two are directly connected, and the delay is stable throughout the day. Pulling the data stream through websocket can run the local 1Gbps broadband. If the target host is also in Singapore, the effect is the best. For telecom, due to the two-way NTT, the network experience is very bad, and it is not recommended to choose the node in Singapore. China Unicom has directly bypassed European Telia, delaying and telecommunications next door.

Only mobile users are recommended to use the Singapore node. Friends who want to build a website through Gcorelabs can use DNSPod or HUAWEI CLOUD DNS resolution service to offload mobile to the Singapore node.

Seoul

CDN IP segment: 92.223.61.0/24
Actual IPs available for CDN: 92.223.61.21, 92.223.61.23, 92.223.61.30

Both China Telecom and China Unicom use HE for their outbound journeys, leading to all of them going around the United States. China Telecom’s return journey continues to use Level 3 around the United States, while China Unicom uses Singapore Cogentco to return to China. The network delays of both are not ideal. The mobile is much better in comparison, and the two-way travel to Hong Kong Level 3, the delay is still excellent.

For the Seoul area, only mobile use is recommended. If the server of the website is located in Japan, you can consider resolving mobile users to the Seoul area.

Tokyo

CDN IP segment: 92.223.63.0/24
Actual IPs available for CDN: 92.223.63.10-11, 92.223.63.21-29, 92.223.63.254

Since the BGP optimization of Gcorelabs in Tokyo is not very good at present, it is only possible to go to NTT in China at present. It is more powerful at night, so it is not recommended.

Hongkong

CDN IP segment: 92.223.76.0/24, 92.223.84.0/24

Actual IPs available for CDN: 92.223.84.248-254, 92.223.76.20-21, 92.223.76.23-25, 92.223.76.30, 92.223.76.254

Gcorelabs also has access to CMI in Hong Kong, and it is currently in a state of mixed routing. Telecom outbound is NTT and backhaul is CMI; China Unicom’s outbound is NTT, and its backhaul is CMI; There are direct routes around the United States, Japan and Hong Kong. Although the delay stability is affected, the impact on the speed is not very large.

Tips: 92.223.84.0/24 may be inaccessible to telecom users in some areas, but 92.223.76.0/24 does not have this problem.

Krasnoyarsk

CDN IP segment: 92.223.114.0/24

IPs actually available for CDN: 92.223.114.4, 92.223.114.6-9, 92.223.114.11, 92.223.114.254

As a region in central Russia, it is currently known that the nearest RT line backhaul does not go around Europe (now the backhaul of Boli RT goes around Germany), telecommunications and China Unicom are friendly, and mobile is not good.

Moscow

CDN IP segment: 92.223.123.0/24

Actual IP available for CDN: 92.223.123.4-50/59/62

Sophia

CDN IP segment: 5.101.219.0/24

Actual IPs available for CDN: 5.101.219.5-6, 5.101.219.14

Budapest

CDN IP segment: 5.101.217.0/24

Actual IP available for CDN: 5.101.217.4

Burley

CDN IP segment: 92.223.110.0/24

IPs actually available for CDN: 92.223.110.4/7-8, 92.223.110.254

Baili has now fully returned to Europe. Although it is very close to China, its value is not high.

sao paulo

CDN IP segment: 92.223.12.0/24

Actual IP available for CDN: 92.223.12.4-5/8-9

Santa Clara

CDN IP segment: 92.223.120.0/24

Actual IP available for CDN: 92.223.120.10/12-15/244

Amsterdam

CDN IP segment: 92.223.126.0/24

Actual IP available for CDN: 92.223.126.18-62

samara

CDN IP segment: 92.223.43.0/24

IP of the actual CDN available: 92.223.43.12-15/62

All scanned CDN IP attachments

https://leo.moe/tools/gcorelabs_ip.txt

This article is reprinted from: https://leo.moe/daily/gcorelabs-cdn.html
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment

Your email address will not be published.