bgpreport

Network · data from 2026-11-12

AS9636 NHNPAYCO-AS-KR-KR - NHNPayco

Registry name: NHNPAYCO-AS-KR-KR - NHNPayco, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9636, 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.146.180.0/23 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS9636 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 36 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none103.146.180.0/23No ROA covers it. Add a ROA for AS9636, maxLength 23.672 of 673
Route object: RIR103.146.180.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

61.252.80.0/20RADBNo ROA
210.221.160.0/20RADBNo ROA
210.221.160.0/21NTTCOMNo ROA
210.221.160.32/27NTTCOMNo ROA
210.221.160.64/26NTTCOMNo ROA
210.221.160.128/25NTTCOMNo ROA
210.221.162.0/25NTTCOMNo ROA
210.221.162.128/25NTTCOMNo ROA
210.221.163.0/24NTTCOMNo ROA
210.221.163.128/25NTTCOMNo ROA
210.221.164.0/26NTTCOMNo ROA
210.221.164.128/25NTTCOMNo ROA
210.221.165.64/26NTTCOMNo ROA
210.221.165.128/25NTTCOMNo ROA
210.221.166.0/25NTTCOMNo ROA
210.221.166.128/25NTTCOMNo ROA
210.221.167.0/26NTTCOMNo ROA
210.221.167.128/25NTTCOMNo ROA
210.221.168.0/21NTTCOMNo ROA
210.221.168.0/26NTTCOMNo ROA
210.221.168.192/27NTTCOMNo ROA
210.221.169.0/27NTTCOMNo ROA
210.221.169.64/29NTTCOMNo ROA
210.221.169.128/26NTTCOMNo ROA
210.221.170.0/26NTTCOMNo ROA
210.221.170.64/26NTTCOMNo ROA
210.221.170.128/25NTTCOMNo ROA
210.221.171.0/25NTTCOMNo ROA
210.221.171.128/25NTTCOMNo ROA
210.221.172.0/25NTTCOMNo ROA
210.221.172.128/25NTTCOMNo ROA
210.221.173.0/25NTTCOMNo ROA
210.221.173.128/25NTTCOMNo ROA
210.221.175.0/25NTTCOMNo 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.