bgpreport

Network · data from 2026-11-12

AS9851 PRO-AS-KR-KR - KOREA UNIVERSITY OF MEDIA ARTS

Registry name: PRO-AS-KR-KR - KOREA UNIVERSITY OF MEDIA ARTS, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9851, 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.
1.227.168.0/24 No ROA Nonecovered by 1.227.168.0/21 673 100% 67
210.106.64.0/21 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS9851 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none1.227.168.0/24No ROA covers it. Add a ROA for AS9851, maxLength 24.673 of 673
Route object: none1.227.168.0/24No route object for it. A route object for 1.227.168.0/21 with origin AS9851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9851 in the RIR database for the space.673 of 673
ROA: none210.106.64.0/21No ROA covers it. Add a ROA for AS9851, maxLength 21.673 of 673
Route object: RIR210.106.64.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

1.227.168.0/21NTTCOMNo ROA
1.227.176.0/22NTTCOMNo ROA
1.227.180.0/23NTTCOMNo ROA
218.150.172.0/22RADBNo 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.