bgpreport

Network · data from 2026-11-12

AS133478 TENCENT-AS-AP - Tencent Cloud Computing (Beijing) Co., Ltd

Registry name: TENCENT-AS-AP - Tencent Cloud Computing (Beijing) Co., Ltd, CN · not in PeeringDB

7IPv4 routes 85.7% RPKI valid · 100.0% with a route object
6IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
96Route objects not announced registered with origin AS133478, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133478, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

103.95.227.0/24 No ROA Other IRR onlyRADB 668 99% 67
142.86.254.0/24 Valid RIR databaseAPNIC 672 100% 67
103.95.225.0/24 Valid RIR databaseAPNIC 671 100% 66
142.86.252.0/24 Valid RIR databaseAPNIC 671 100% 66
103.95.226.0/24 Valid RIR databaseAPNIC 670 100% 67
142.86.253.0/24 Valid RIR databaseAPNIC 670 100% 67
103.95.224.0/24 Valid RIR databaseAPNIC 668 99% 67
240d:c000:f1e0::/48 Valid RIR databaseAPNIC 636 100% 69
240d:c000:f1ef::/48 Valid RIR databaseAPNIC 636 100% 68
240d:c000:f1e1::/48 Valid RIR databaseAPNIC 635 100% 67
240d:c000:f1e3::/48 Valid RIR databaseAPNIC 635 100% 67
240d:c000:f1e4::/48 Valid RIR databaseAPNIC 634 100% 67
240d:c000:f1e5::/48 Valid RIR databaseAPNIC 634 100% 67

AS-SET

AS133478 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 98 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced96
ChangePrefix or setDetailFull-table peers
ROA: none103.95.227.0/24No ROA covers it. Add a ROA for AS133478, maxLength 24.668 of 673
Route object: RIR103.95.227.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

Route objects with origin AS133478 whose prefix no peer sees AS133478 announce. Many are kept on purpose (backup routes, space announced only in some places).

19.28.0.0/23NTTCOM, RADBNo ROA
19.28.0.0/24NTTCOM, RADBNo ROA
19.28.1.0/24NTTCOM, RADBNo ROA
119.28.0.0/16NTTCOM, RADBNo ROA
119.28.0.0/17NTTCOM, RADBNo ROA
119.28.0.0/18APNICInvalid: origin
119.28.64.0/18NTTCOM, RADBNo ROA
119.28.64.0/19APNICInvalid: origin
119.28.96.0/20APNICInvalid: origin
119.28.112.0/20APNICInvalid: origin
119.28.128.0/17NTTCOM, RADBNo ROA
119.28.128.0/18NTTCOM, RADBNo ROA
119.28.128.0/19NTTCOM, RADBNo ROA
119.28.160.0/19NTTCOM, RADBNo ROA
119.28.160.0/20NTTCOM, RADBNo ROA
119.28.160.0/21NTTCOM, RADBNo ROA
119.28.164.0/22NTTCOM, RADBNo ROA
119.28.164.0/23NTTCOM, RADBNo ROA
119.28.168.0/21NTTCOM, RADBNo ROA
119.28.168.0/22NTTCOM, RADBNo ROA
119.28.172.0/22NTTCOM, RADBNo ROA
119.28.176.0/20NTTCOM, RADBNo ROA
119.28.176.0/21NTTCOM, RADBNo ROA
119.28.176.0/22NTTCOM, RADBNo ROA
119.28.180.0/22NTTCOM, RADBNo ROA
119.28.184.0/21NTTCOM, RADBNo ROA
119.28.184.0/22NTTCOM, RADBNo ROA
119.28.188.0/22NTTCOM, RADBNo ROA
119.28.192.0/18NTTCOM, RADBNo ROA
119.28.192.0/19NTTCOM, RADBNo ROA
119.28.192.0/20NTTCOM, RADBNo ROA
119.28.192.0/21NTTCOM, RADBNo ROA
119.28.192.0/22NTTCOM, RADBNo ROA
119.28.196.0/22NTTCOM, RADBNo ROA
119.28.200.0/21NTTCOM, RADBNo ROA
119.28.200.0/22NTTCOM, RADBNo ROA
119.28.204.0/22NTTCOM, RADBNo ROA
119.28.208.0/20NTTCOM, RADBNo ROA
119.28.208.0/21NTTCOM, RADBNo ROA
119.28.208.0/22NTTCOM, RADBNo ROA
119.28.212.0/22NTTCOM, RADBNo ROA
119.28.216.0/21NTTCOM, RADBNo ROA
119.28.216.0/22NTTCOM, RADBNo ROA
119.28.220.0/22NTTCOM, RADBNo ROA
119.28.224.0/19NTTCOM, RADBNo ROA
119.28.224.0/20NTTCOM, RADBNo ROA
119.28.224.0/21NTTCOM, RADBNo ROA
119.28.224.0/22NTTCOM, RADBNo ROA
119.28.228.0/22NTTCOM, RADBNo ROA
119.28.240.0/20NTTCOM, RADBNo ROA
119.28.240.0/21NTTCOM, RADBNo ROA
119.28.240.0/22NTTCOM, RADBNo ROA
119.28.240.0/23NTTCOM, RADBNo ROA
119.28.240.0/24NTTCOM, RADBNo ROA
119.28.241.0/24NTTCOM, RADBNo ROA
119.28.242.0/23NTTCOM, RADBNo ROA
119.28.242.0/24NTTCOM, RADBNo ROA
119.28.243.0/24NTTCOM, RADBNo ROA
119.28.244.0/22NTTCOM, RADBNo ROA
119.28.244.0/23NTTCOM, RADBNo ROA
119.28.244.0/24NTTCOM, RADBNo ROA
119.28.245.0/24NTTCOM, RADBNo ROA
119.28.246.0/23NTTCOM, RADBNo ROA
119.28.246.0/24NTTCOM, RADBNo ROA
119.28.247.0/24NTTCOM, RADBNo ROA
119.28.248.0/21NTTCOM, RADBNo ROA
119.28.248.0/22NTTCOM, RADBNo ROA
119.28.248.0/23NTTCOM, RADBNo ROA
119.28.248.0/24NTTCOM, RADBNo ROA
119.28.249.0/24NTTCOM, RADBNo ROA
119.28.250.0/23NTTCOM, RADBNo ROA
119.28.250.0/24NTTCOM, RADBNo ROA
119.28.251.0/24NTTCOM, RADBNo ROA
119.28.252.0/22NTTCOM, RADBNo ROA
119.28.252.0/23NTTCOM, RADBNo ROA
119.28.252.0/24NTTCOM, RADBNo ROA
119.28.253.0/24NTTCOM, RADBNo ROA
119.28.254.0/23NTTCOM, RADBNo ROA
119.28.254.0/24NTTCOM, RADBNo ROA
119.28.255.0/24NTTCOM, RADBNo ROA
203.205.136.0/22NTTCOM, RADBNo ROA
203.205.136.0/23NTTCOM, RADBNo ROA
203.205.140.0/22NTTCOM, RADBNo ROA
203.205.140.0/23NTTCOM, RADBNo ROA
203.205.142.0/23NTTCOM, RADBNo ROA
203.205.144.0/22NTTCOM, RADBNo ROA
203.205.144.0/23NTTCOM, RADBNo ROA
203.205.146.0/23NTTCOM, RADBNo ROA
203.205.148.0/22NTTCOM, RADBNo ROA
203.205.148.0/23NTTCOM, RADBNo ROA
203.205.148.0/24NTTCOM, RADBNo ROA
203.205.149.0/24NTTCOM, RADBNo ROA
203.205.150.0/23NTTCOM, RADBNo ROA
203.205.150.0/24NTTCOM, RADBNo ROA
203.205.151.0/24NTTCOM, RADBNo ROA
240d:c000:f1ef::/64APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.