小板

小板的中大型碎碎念

HomeArchives版权声明微型碎碎念(telegram)

Bilibili's 93 Tribute - Overseas Locking of Bilibili's CDN IP

#bilibili#cdn14
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
As the 93rd anniversary military parade approaches, the international CDN performance of Bilibili (B站) has significantly declined, particularly in Australia, where speeds have dropped to as low as 8 kBps. This issue with Bilibili's international CDN has been longstanding, influenced by various factors including the company's reliance on Tencent Cloud and Akamai for content delivery. The analysis reveals that Bilibili's CDN architecture is primarily based on Tencent Cloud, which has been in place since the company's early cloud adoption. Akamai's performance has been criticized for being poor, with cold parsing and inadequate resource distribution. In contrast, Alibaba Cloud is noted for better performance, while Huawei Cloud is mentioned as less frequently used. The discussion also touches on Bilibili's domestic parsing issues and the need for improvements in their CDN strategy, particularly in adopting advanced technologies like PCDN (Peer-to-Peer Content Delivery Network). Despite being a competitor to Douyu, Bilibili has lagged in this area, indicating a need for strategic enhancements to improve overall performance.

Preface#

As the 93rd anniversary parade approaches, the international routes of Bilibili have become increasingly bizarre. Taking Victoria, Australia as an example, previously, the CDN's download speed would sometimes reach around 300 kBps, especially for newly launched resources that had not been widely transcoded or distributed at the end.

However, in recent days, there have been terrifyingly low speeds of 8 kBps... What are you saying? Celebrating 93? What are you doing making a fuss on a site that is on the same track as 91?

Analysis#

In fact, Bilibili's international CDN source issue has been longstanding.

Based on some field shares I've heard from people, my work experience in domestic companies, and a few public articles (like https://www.bilibili.com/opus/923445482234052759), along with Bilibili's previous Go source code (not very useful), it appears that Bilibili's CDN architecture mainly consists of:

  1. Domestic Tencent Cloud, taking upos-sz-staticcos.bilivideo.com.cdn.dnsv1.com as an example.
;; ANSWER SECTION:
upos-sz-staticcos.bilivideo.com. 190 IN	CNAME	upos-sz-staticcos.bilivideo.com.cdn.dnsv1.com [Tencent Cloud CDN] .
upos-sz-staticcos.bilivideo.com.cdn.dnsv1.com [Tencent Cloud CDN] . 230 IN CNAME ty-staticcos.sched.dma-dk.tdnsdl1.cn.
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	221.204.209.235 [Taiyuan, Shanxi Unicom]
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	218.24.84.120 [Shenyang, Liaoning Unicom]
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	221.204.209.188 [Taiyuan, Shanxi Unicom]
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	119.188.180.188 [Jinan, Shandong Unicom/IDC]
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	116.131.56.179 [Beijing New Guo Xin Communication Co., Ltd.]
ty-staticcos.sched.dma-dk.tdnsdl1.cn. 55 IN A	221.204.209.227 [Taiyuan, Shanxi Unicom]

This belongs to a higher tier of Tencent Cloud customers, a service that was launched when Tencent invested back then, and is among the earlier cloud services of Bilibili. At that time, I happened to be in CSIG and heard some rumors.

  1. Akamai, which should have been integrated around the time of Bilibili's IPO, while writing internationalization stories? The reputation... is very poor... The parsing is very cold, the depth is shallow, the exit is cold, and the source strategy/line configuration is confusing, compounded by insufficient hot parsing, so obscure resources can easily flow. Although there is no actual evidence, it's clear to anyone with eyes that this thing didn't cost much.
;; ANSWER SECTION:
upos-hz-mirrorakam.akamaized.net [Akamai CDN] . 10 IN	CNAME	globalredir.upos-hz-mirrorakam.akadns.net [Akamai CDN] .
globalredir.upos-hz-mirrorakam.akadns.net [Akamai CDN] . 10 IN CNAME a1893.dscw10.akamai.net [Akamai CDN] .
a1893.dscw10.akamai.net [Akamai CDN] . 10	IN	A	23.192.239.225 [Akamai node in Australia]
a1893.dscw10.akamai.net [Akamai CDN] . 10	IN	A	23.192.239.214 [Akamai node in Australia]
a1893.dscw10.akamai.net [Akamai CDN] . 10	IN	A	23.192.239.247 [Akamai node in Australia]
a1893.dscw10.akamai.net [Akamai CDN] . 10	IN	A	23.192.239.239 [Akamai node in Australia]

Sometimes I even wonder if Australia is just a mountain next to Pangong Lake in Tibet.

  1. Alibaba Cloud, Uncle has activated skills to balance.

Alibaba Cloud is not that bad.

International (Lame Cow!)#

;; ANSWER SECTION:
upos-sz-mirroraliov.bilivideo.com. 10 IN CNAME	upos-sz-mirroraliov.bilivideo.com.queniuaa.com.
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.177 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.178 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.176 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.175 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.172 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.174 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.171 [Alibaba Cloud CDN node in Sydney, Australia]
upos-sz-mirroraliov.bilivideo.com.queniuaa.com.	10 IN A	47.246.41.173 [Alibaba Cloud CDN node in Sydney, Australia]

China (Kunlun!)#

;; ANSWER SECTION:
upos-sz-mirrorali02.bilivideo.com. 600 IN CNAME	upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] .
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 61.170.81.223 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 61.170.80.221 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 180.163.147.218 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 180.163.148.198 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 61.170.79.107 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 101.89.125.248 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 101.226.26.145 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 101.226.28.234 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 222.73.33.10 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 101.226.27.72 [Shanghai Telecom]
upos-sz-mirrorali02.bilivideo.com.w.kunluncan.com [Alibaba Cloud CDN] . 60 IN A 61.170.81.224 [Shanghai Telecom]

Although Kunlun Mountain is not far from Pangong Lake, it is much better. However, the naming of Alibaba's "Shan Hai Jing" is indeed abstract.

  1. Huawei
;; ANSWER SECTION:
d1--cn-gotcha208b.bilivideo.com. 458 IN CNAME   d1--cn-gotcha208b.bilivideo.com.04f6a54d.c.cdnhwc1.com [Huawei Cloud CDN] .
d1--cn-gotcha208b.bilivideo.com.04f6a54d.c.cdnhwc1.com [Huawei Cloud CDN] .   60 IN CNAME hcdnv.hlsv76.cdnhwcibv122.com.
hcdnv.hlsv76.cdnhwcibv122.com. 60 IN    A       183.61.225.73 [China–Guangdong–Dongguan Telecom]
hcdnv.hlsv76.cdnhwcibv122.com. 60 IN    A       183.61.225.72 [China–Guangdong–Dongguan Telecom]
hcdnv.hlsv76.cdnhwcibv122.com. 60 IN    A       27.159.90.77 [China–Fujian–Xiamen Telecom]
hcdnv.hlsv76.cdnhwcibv122.com. 60 IN    A       27.159.90.75 [China–Fujian–Xiamen Telecom]

In fact, there isn't much to say about Huawei; it's rarely assigned. Huawei is suffering. I can't say anything; if I do, I'll be in trouble.

  1. Self-operated, Uncle's strict selection.

In fact, it can't be called self-operated; many lines actually go through Tencent Cloud's exit. After the 2024 operator war, Uncle has prepared for both family and business, buying provincial-level exits in many places in China, mainly from China Mobile, quietly making a fortune.

However, Bilibili's domestic parsing... is also a mess, besides frequently crossing provinces, there’s also ⬇️

  1. Open! PCDN! Open! Let the situation reverse!

Uncle has never been stingy when it comes to saving money. After Douyu went public, it lagged behind Douyu for a long time in PCDN. You should know that Douyu tried PCDN during the Flash player era. If we talk about technology, they are indeed somewhat impressive in this regard; the final results are not to be discussed, but advanced technology should be used first, and the benefits of Chrome are steadily reaped. Douyu can be said to be closely following the development of WebRTC. You think I'm Douyu? In fact, my name is Douyu Meeting.

Uncle's PCDN performance is not ideal. *.szbdyd.com is Uncle's pale report card. However, Uncle is not very cultured and hasn't read "Shan Hai Jing," so I don't know what this abbreviation means.

When I was in Shanghai, after the 2024 cross-province war, the traffic of this domain name started to rise sharply. The method at that time was quite simple; I just blocked it in the rules of Clash and QX, and it was easy and pleasant.

Current Situation#

MD, the problem is that I can still use script (https://github.com/Kanda-Akihito-Kun/ccb) to change the source on the web, but what about mobile devices? I can't use QX and Clash anymore.

Every time this happens, I silently recite the benefits of the GFW; without the Great Firewall, my understanding of network planning would not be so deep, nor would I have the professional advantage of being an early starter. Let's say thank you to the Great Firewall!

So today, I can only reluctantly add a few AdGuard rules to manually specify a CNAME for Uncle.

image

Will Get#

image

Just hijack upos-sz-staticcos.bilivideo.com to the subdomain you want to specify. If your technology does not support CNAME rewriting, directly writing the IP in hosts is also fine.

In fact, for convenience, directly hijacking *.bilivideo.com is even more convenient. According to tests, some live streaming traffic also goes through here and can be normally transferred.

I personally recommend going directly to machines in Hong Kong because although Alibaba Cloud is good, Alibaba's source strategy has a scraping mode, which can occasionally act up in extreme situations.

Links#

Conclusion#

When checking subdomains, I found that Uncle actually uses Let's Encrypt for many certificates, which is indeed a sign of being a poor uncle. The stereotype of the two-dimensional world has deepened again.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.