bgpreport

Network · data from 2026-11-12

AS9973 BSITC-AS-KR-KR - BSITC

Registry name: BSITC-AS-KR-KR - BSITC, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9973, 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.
61.252.172.0/22 No ROA Other IRR onlyRADB 670 100% 67
103.106.140.0/22 No ROA Other IRR onlyRADB 670 100% 67
202.124.254.0/24 No ROA Other IRR onlyRADB 670 100% 67
202.124.255.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.227.88.0/22 No ROA Other IRR onlyRADB 670 100% 67
203.231.136.0/22 No ROA Other IRR onlyRADB 670 100% 67
203.235.22.0/23 No ROA Other IRR onlyRADB 670 100% 67
203.235.128.0/22 No ROA Other IRR onlyRADB 670 100% 67
203.236.176.0/22 No ROA Other IRR onlyRADB 670 100% 67
203.238.106.0/24 No ROA Other IRR onlyRADB 670 100% 67
203.238.107.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS9973 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 41 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none61.252.172.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR61.252.172.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none103.106.140.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR103.106.140.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.124.254.0/24No ROA covers it. Add a ROA for AS9973, maxLength 24.670 of 673
Route object: RIR202.124.254.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.124.255.0/24No ROA covers it. Add a ROA for AS9973, maxLength 24.670 of 673
Route object: RIR202.124.255.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.227.88.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR203.227.88.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.231.136.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR203.231.136.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.235.22.0/23No ROA covers it. Add a ROA for AS9973, maxLength 23.670 of 673
Route object: RIR203.235.22.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.235.128.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR203.235.128.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.236.176.0/22No ROA covers it. Add a ROA for AS9973, maxLength 22.670 of 673
Route object: RIR203.236.176.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.238.106.0/24No ROA covers it. Add a ROA for AS9973, maxLength 24.670 of 673
Route object: RIR203.238.106.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.238.107.0/24No ROA covers it. Add a ROA for AS9973, maxLength 24.670 of 673
Route object: RIR203.238.107.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

1.16.64.0/22RADBNo ROA
1.209.211.0/24RADBNo ROA
1.227.61.0/24RADBNo ROA
175.118.115.0/24RADBNo ROA
182.50.16.0/20RADBNo ROA
182.50.22.0/24RADBNo ROA
182.50.24.0/24RADBNo ROA
182.50.25.0/24RADBNo ROA
182.50.26.0/24RADBNo ROA
182.50.27.0/24RADBNo ROA
182.50.28.0/24RADBNo ROA
182.50.29.0/24RADBNo ROA
210.121.183.0/24RADBNo ROA
211.45.218.0/24RADBNo ROA
211.45.222.0/24RADBNo ROA
211.45.228.0/24RADBNo ROA
211.45.230.0/24RADBNo ROA
211.110.95.0/24RADBNo ROA
211.181.232.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.