bgpreport

Network · data from 2026-11-12

AS133448 CHGPL-AS-AP - Korea

Registry name: CHGPL-AS-AP - Korea, HK · not in PeeringDB

15IPv4 routes 60.0% RPKI valid · 60.0% with a route object
0IPv6 routes
6RPKI invalid 6 origin · 0 maxLength
0No ROA 6 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS133448, seen from no peer

Announced routes

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

45.200.140.0/24 Invalid: origin Other origin only 1 0%low visibility 1
45.200.141.0/24 Invalid: origin Other origin only 1 0%low visibility 1
154.89.8.0/24 Invalid: origin None 1 0%low visibility 1
154.89.9.0/24 Invalid: origin None 1 0%low visibility 1
154.89.10.0/24 Invalid: origin None 1 0%low visibility 1
154.89.11.0/24 Invalid: origin None 1 0%low visibility 1
101.55.59.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.86.85.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.86.87.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.101.188.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
119.42.33.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.204.19.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
45.204.22.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
45.204.23.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
103.229.226.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS133448 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 27 are in fix.csv.

  • ROA: origin6
  • Route object: none6
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin45.200.140.0/24ROAs covering it name AS11404, AS17561, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none45.200.140.0/24Route objects for it name AS17561. Add a route object with origin AS133448 in the RIR database for the space.1 of 673
ROA: origin45.200.141.0/24ROAs covering it name AS11404, AS17561, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none45.200.141.0/24Route objects for it name AS17561. Add a route object with origin AS133448 in the RIR database for the space.1 of 673
ROA: origin154.89.8.0/24ROAs covering it name AS17561, AS131274, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none154.89.8.0/24No route object for it. Add a route object with origin AS133448 in the RIR database for the space.1 of 673
ROA: origin154.89.9.0/24ROAs covering it name AS17561, AS131274, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none154.89.9.0/24No route object for it. Add a route object with origin AS133448 in the RIR database for the space.1 of 673
ROA: origin154.89.10.0/24ROAs covering it name AS17561, AS131274, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none154.89.10.0/24No route object for it. Add a route object with origin AS133448 in the RIR database for the space.1 of 673
ROA: origin154.89.11.0/24ROAs covering it name AS17561, AS131274, not AS133448. If AS133448 should announce it, add a ROA for AS133448.1 of 673
Route object: none154.89.11.0/24No route object for it. Add a route object with origin AS133448 in the RIR database for the space.1 of 673

Route objects not announced

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

45.207.4.0/23RADBNo ROA
103.86.84.0/22RADBNo ROA
103.101.188.0/22RADBNo ROA
103.108.184.0/23RADBNo ROA
103.116.132.0/23RADBNo ROA
103.229.227.0/24APNICValid
119.42.35.0/24APNIC, RADBValid
139.5.176.0/24APNIC, RADBValid
154.92.4.0/22RADBNo ROA
154.196.2.0/23RADBNo ROA
154.218.2.0/23RADBNo ROA
154.223.1.0/24AFRINIC, NTTCOM, RADBValid
154.223.2.0/24AFRINIC, NTTCOM, RADBValid
154.223.4.0/24AFRINIC, NTTCOM, RADBValid
2001:df4:1500::/48RADBNo 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.