bgpreport

Network · data from 2026-11-12

AS4040 KORNET-PS-AS-KR-KR - Korea Telecom

Registry name: KORNET-PS-AS-KR-KR - Korea Telecom, 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
62Route objects not announced registered with origin AS4040, seen from no peer

Announced routes

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

14.49.22.0/24 No ROA Other IRR onlyRADB 119 18% 43

AS-SET

AS4040 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 64 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced62
ChangePrefix or setDetailFull-table peers
ROA: none14.49.22.0/24No ROA covers it. Add a ROA for AS4040, maxLength 24.119 of 673
Route object: RIR14.49.22.0/24Route object only in RADB. Add it in the RIR database for the space.119 of 673

Route objects not announced

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

14.49.13.0/24RADBNo ROA
14.49.14.0/24RADBNo ROA
14.49.19.0/24RADBNo ROA
49.254.161.0/24RADBNo ROA
61.78.51.0/24RADBNo ROA
103.150.62.0/24RADBNo ROA
112.175.174.0/24RADBNo ROA
112.175.175.0/24RADBNo ROA
112.175.178.0/24RADBNo ROA
115.144.255.0/24RADBNo ROA
121.156.64.0/24RADBNo ROA
175.207.5.0/24RADBNo ROA
175.207.6.0/24RADBNo ROA
175.207.16.0/24RADBNo ROA
175.207.17.0/24RADBNo ROA
175.207.18.0/24RADBNo ROA
183.110.33.0/24RADBNo ROA
183.110.35.0/24RADBNo ROA
183.110.36.0/24RADBNo ROA
183.110.38.0/24RADBNo ROA
183.110.40.0/24RADBNo ROA
183.110.41.0/24RADBNo ROA
183.110.58.0/24RADBNo ROA
183.110.60.0/24RADBNo ROA
183.110.80.0/24RADBNo ROA
183.110.82.0/24RADBNo ROA
183.110.83.0/24RADBNo ROA
183.110.84.0/24RADBNo ROA
183.110.87.0/24RADBNo ROA
183.110.88.0/24RADBNo ROA
183.110.89.0/24RADBNo ROA
183.110.90.0/24RADBNo ROA
183.110.91.0/24RADBNo ROA
183.110.92.0/24RADBNo ROA
183.110.93.0/24RADBNo ROA
183.110.94.0/24RADBNo ROA
183.110.95.0/24RADBNo ROA
183.110.96.0/24RADBNo ROA
183.110.97.0/24RADBNo ROA
183.110.98.0/24RADBNo ROA
183.110.99.0/24RADBNo ROA
183.110.100.0/24RADBNo ROA
183.110.101.0/24RADBNo ROA
183.110.102.0/24RADBNo ROA
183.110.204.0/24RADBNo ROA
183.110.205.0/24RADBNo ROA
202.14.165.0/24RADBNo ROA
203.234.144.0/24RADBNo ROA
211.39.152.0/24RADBNo ROA
211.39.153.0/24RADBNo ROA
211.39.157.0/24RADBNo ROA
218.145.58.0/24RADBNo ROA
218.145.59.0/24RADBNo ROA
220.73.218.0/24RADBNo ROA
220.73.221.0/24RADBNo ROA
220.90.199.0/24RADBNo ROA
220.95.224.0/24RADBNo ROA
220.95.227.0/24RADBNo ROA
222.122.54.0/24RADBNo ROA
222.122.75.0/24RADBNo ROA
222.122.216.0/24RADBNo ROA
222.122.217.0/24RADBNo 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.