bgpreport

Network · data from 2026-11-12

AS133955 WLINCL-AS - World-Link International

Registry name: WLINCL-AS - World-Link International, HK · not in PeeringDB

11IPv4 routes 81.8% RPKI valid · 90.9% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
81Route objects not announced registered with origin AS133955, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133955, 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.

150.129.211.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.235.6.0/24 Invalid: origin RIR databaseAPNIC, RADB 2 0%low visibility 2
223.165.8.0/24 Valid Other IRR onlyRADB 672 100% 66
223.165.9.0/24 Valid Other IRR onlyRADB 672 100% 66
223.165.10.0/24 Valid Other IRR onlyRADB 672 100% 67
223.165.12.0/24 Valid Other IRR onlyRADB 672 100% 67
223.165.13.0/24 Valid Other IRR onlyRADB 671 100% 67
223.165.15.0/24 Valid Other IRR onlyRADB 671 100% 67
103.235.5.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
150.129.210.0/24 Valid RIR databaseAPNIC 672 100% 67
103.235.4.0/24 Valid RIR databaseAPNIC 209 31% 55

AS-SET

AS133955 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 90 are in fix.csv.

  • ROA: origin2
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced81
ChangePrefix or setDetailFull-table peers
ROA: origin150.129.211.0/24ROAs covering it name AS7656, not AS133955. If AS133955 should announce it, add a ROA for AS133955.2 of 673
Route object: none150.129.211.0/24Route objects for it name AS7656. Add a route object with origin AS133955 in the RIR database for the space.2 of 673
ROA: origin103.235.6.0/24ROAs covering it name AS7656, not AS133955. If AS133955 should announce it, add a ROA for AS133955.2 of 673
Route object: RIR223.165.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.165.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.165.10.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.165.12.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.165.13.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR223.165.15.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

23.249.207.0/24RADBNo ROA
42.1.22.0/24RADBNo ROA
42.128.201.0/24NTTCOM, RADBNo ROA
42.156.100.0/24RADBNo ROA
42.187.89.0/24RADBNo ROA
50.117.255.0/24RADBNo ROA
65.111.159.0/24RADBNo ROA
66.6.63.0/24RADBNo ROA
66.220.207.0/24RADBNo ROA
67.201.143.0/24RADBNo ROA
72.45.127.0/24RADBNo ROA
74.127.255.0/24RADBNo ROA
74.205.191.0/24RADBNo ROA
101.101.86.0/24RADBNo ROA
101.110.89.0/24RADBNo ROA
101.192.201.0/24NTTCOM, RADBNo ROA
101.192.231.0/24NTTCOM, RADBNo ROA
101.203.149.0/24RADBNo ROA
103.235.7.0/24APNICValid
104.129.239.0/24RADBNo ROA
104.156.47.0/24RADBNo ROA
104.224.127.0/24RADBNo ROA
110.93.50.0/24RADBNo ROA
110.173.79.0/24RADBNo ROA
118.127.148.0/24RADBNo ROA
119.27.149.0/24RADBNo ROA
119.151.209.0/24RADBNo ROA
119.151.247.0/24RADBNo ROA
120.143.138.0/24RADBNo ROA
121.46.218.0/24NTTCOM, RADBNo ROA
122.98.121.0/24NTTCOM, RADBNo ROA
122.98.123.0/24NTTCOM, RADBNo ROA
123.50.186.0/24RADBNo ROA
124.242.154.0/24NTTCOM, RADBNo ROA
128.57.187.0/24RADBNo ROA
128.57.197.0/24RADBNo ROA
128.57.207.0/24RADBNo ROA
128.144.255.0/24RADBNo ROA
131.195.255.0/24RADBNo ROA
135.12.255.0/24RADBNo ROA
138.11.255.0/24RADBNo ROA
139.173.255.0/24RADBNo ROA
139.183.181.0/24NTTCOM, RADBNo ROA
139.183.222.0/24NTTCOM, RADBNo ROA
142.10.255.0/24RADBNo ROA
142.128.255.0/24RADBNo ROA
142.148.127.0/24RADBNo ROA
144.7.198.0/24RADBNo ROA
144.68.75.0/24RADBNo ROA
144.68.76.0/24RADBNo ROA
144.68.77.0/24RADBNo ROA
144.68.78.0/24RADBNo ROA
144.68.79.0/24RADBNo ROA
144.68.80.0/24RADBNo ROA
144.68.81.0/24RADBNo ROA
144.68.82.0/24RADBNo ROA
144.68.83.0/24RADBNo ROA
144.68.84.0/24RADBNo ROA
144.68.85.0/24RADBNo ROA
144.68.86.0/24RADBNo ROA
144.68.87.0/24RADBNo ROA
144.68.88.0/24RADBNo ROA
144.68.89.0/24RADBNo ROA
144.68.90.0/24RADBNo ROA
144.68.91.0/24RADBNo ROA
144.68.92.0/24RADBNo ROA
144.68.93.0/24RADBNo ROA
144.68.94.0/24RADBNo ROA
150.129.208.0/24APNICValid
153.50.90.0/24RADBNo ROA
155.20.199.0/24RADBNo ROA
161.183.179.0/24RADBNo ROA
161.183.189.0/24RADBNo ROA
161.183.198.0/24RADBNo ROA
162.126.121.0/24RADBNo ROA
162.135.121.0/24RADBNo ROA
164.208.102.0/24RADBNo ROA
169.148.201.0/24RADBNo ROA
170.14.201.0/24RADBNo ROA
170.113.100.0/24RADBNo ROA
170.127.100.0/24RADBNo ROA

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.