bgpreport

Network · data from 2026-11-12

AS9639 ARTISTCOMPANY-AS-KR-KR - Artist Company Inc.

Registry name: ARTISTCOMPANY-AS-KR-KR - Artist Company Inc., KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9639, 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.105.156.0/23 No ROA Nonecovered by 103.105.156.0/22 673 100% 67
103.105.158.0/23 No ROA Nonecovered by 103.105.156.0/22 673 100% 67
103.105.156.0/22 No ROA Other IRR onlyRADB 673 100% 67
2402:bcc0::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS9639 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 17 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none103.105.156.0/23No ROA covers it. Add a ROA for AS9639, maxLength 23.673 of 673
Route object: none103.105.156.0/23No route object for it. A route object for 103.105.156.0/22 with origin AS9639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9639 in the RIR database for the space.673 of 673
ROA: none103.105.158.0/23No ROA covers it. Add a ROA for AS9639, maxLength 23.673 of 673
Route object: none103.105.158.0/23No route object for it. A route object for 103.105.156.0/22 with origin AS9639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9639 in the RIR database for the space.673 of 673
ROA: none103.105.156.0/22No ROA covers it. Add a ROA for AS9639, maxLength 22.673 of 673
Route object: RIR103.105.156.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2402:bcc0::/32No ROA covers it. Add a ROA for AS9639, maxLength 32.634 of 636
Route object: RIR2402:bcc0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

203.237.240.0/22RADBNo ROA
203.237.244.0/22RADBNo ROA
210.102.232.0/22RADBNo ROA
210.119.204.0/24RADBNo ROA
210.119.205.0/24RADBNo ROA
210.119.206.0/24RADBNo ROA
211.220.213.0/24RADBNo ROA
211.220.214.0/24RADBNo ROA
218.233.220.0/25RADBNo 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.