bgpreport

Network · data from 2026-11-12

AS135967 Bach Kim Network Solutions

Registry name: BKNS-AS-VN - Bach Kim Network solutions Join stock company, VN · PeeringDB

20IPv4 routes 90.0% RPKI valid · 90.0% with a route object
12IPv6 routes 91.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS135967, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS135967, 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.79.140.0/23 No ROA Nonecovered by 103.79.140.0/22 2 0%low visibility 2
103.79.142.0/23 No ROA Nonecovered by 103.79.140.0/22 2 0%low visibility 2
2400:7ea0::/48 No ROA Other IRR onlyRADB 636 100% 69
103.162.30.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
42.96.12.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.3.244.0/24 Valid RIR databaseAPNIC 673 100% 66
103.3.247.0/24 Valid RIR databaseAPNIC 673 100% 66
103.74.120.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.74.122.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.147.126.0/23 Valid RIR databaseAPNIC 673 100% 66
103.163.216.0/23 Valid RIR databaseAPNIC 673 100% 66
42.96.4.0/23 Valid RIR databaseAPNIC 672 100% 66
103.3.245.0/24 Valid RIR databaseAPNIC 672 100% 66
103.3.246.0/24 Valid RIR databaseAPNIC 672 100% 66
103.121.88.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.121.90.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.161.16.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.187.168.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
160.30.86.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
45.124.84.0/24 Valid RIR databaseAPNIC 671 100% 66
2001:df4:2540::/48 Valid RIR databaseAPNIC 636 100% 69
2403:6a40::/48 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:2::/48 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:1000::/36 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:2000::/36 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:3000::/36 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:4000::/36 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:5000::/36 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:e000::/36 Valid RIR databaseAPNIC 636 100% 69
2407:2ec0::/48 Valid RIR databaseAPNIC 636 100% 69
2403:6a40:f000::/36 Valid RIR databaseAPNIC 635 100% 69
103.176.250.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS135967's PeeringDB record names no 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 16 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none103.79.140.0/23No ROA covers it. Add a ROA for AS135967, maxLength 23.2 of 673
Route object: none103.79.140.0/23No route object for it. A route object for 103.79.140.0/22 with origin AS135967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135967 in the RIR database for the space.2 of 673
ROA: none103.79.142.0/23No ROA covers it. Add a ROA for AS135967, maxLength 23.2 of 673
Route object: none103.79.142.0/23No route object for it. A route object for 103.79.140.0/22 with origin AS135967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135967 in the RIR database for the space.2 of 673
ROA: none2400:7ea0::/48No ROA covers it. Add a ROA for AS135967, maxLength 48.636 of 636
Route object: RIR2400:7ea0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR103.162.30.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.3.244.0/22APNICValid
103.79.140.0/22APNICNo ROA
103.161.170.0/23APNICValid
103.161.170.0/24APNICValid
103.161.171.0/24APNICValid
103.176.22.0/23APNICValid
103.180.138.0/23APNICValid
103.188.242.0/23APNICValid
2403:6a40::/32APNICNo 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.