bgpreport

Network · data from 2026-11-12

AS17844 NPS01-AS-KR-KR - National Pension Service

Registry name: NPS01-AS-KR-KR - National Pension Service, 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
29Route objects not announced registered with origin AS17844, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17844, 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.
210.97.37.0/24 No ROA Other origin only 673 100% 67
103.139.84.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS17844 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 33 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none210.97.37.0/24No ROA covers it. Add a ROA for AS17844, maxLength 24.673 of 673
Route object: none210.97.37.0/24Route objects for it name AS9768. Add a route object with origin AS17844 in the RIR database for the space.673 of 673
ROA: none103.139.84.0/24No ROA covers it. Add a ROA for AS17844, maxLength 24.673 of 673
Route object: RIR103.139.84.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

211.115.32.0/19RADBNo ROA
211.115.32.0/23NTTCOM, RADBNo ROA
211.115.34.0/24RADBNo ROA
211.115.35.0/24NTTCOM, RADBNo ROA
211.115.36.0/23NTTCOM, RADBNo ROA
211.115.38.0/23NTTCOM, RADBNo ROA
211.115.40.0/22NTTCOM, RADBNo ROA
211.115.44.0/23NTTCOM, RADBNo ROA
211.115.46.0/24NTTCOM, RADBNo ROA
211.115.47.0/24NTTCOM, RADBNo ROA
211.115.48.0/23NTTCOM, RADBNo ROA
211.115.50.0/23NTTCOM, RADBNo ROA
211.115.52.0/23NTTCOM, RADBNo ROA
211.115.54.0/23NTTCOM, RADBNo ROA
211.115.56.0/23NTTCOM, RADBNo ROA
211.115.58.0/23NTTCOM, RADBNo ROA
211.115.60.0/24NTTCOM, RADBNo ROA
211.115.61.0/24NTTCOM, RADBNo ROA
211.115.62.0/24NTTCOM, RADBNo ROA
211.115.63.0/24NTTCOM, RADBNo ROA
211.172.128.0/20RADBNo ROA
211.172.128.0/23NTTCOM, RADBNo ROA
211.172.130.0/23NTTCOM, RADBNo ROA
211.172.132.0/23NTTCOM, RADBNo ROA
211.172.134.0/23NTTCOM, RADBNo ROA
211.172.136.0/23NTTCOM, RADBNo ROA
211.172.138.0/23NTTCOM, RADBNo ROA
211.172.140.0/23NTTCOM, RADBNo ROA
211.172.142.0/23NTTCOM, RADBNo 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.