bgpreport

Network · data from 2026-11-12

AS45964 EDWARDSKOREA-AS-KR-KR - Edwards korea Limited

Registry name: EDWARDSKOREA-AS-KR-KR - Edwards korea Limited, KR · not in PeeringDB

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

Announced routes

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

111.66.224.0/22 No ROA Other origin onlycovered by 111.66.224.0/19 673 100% 67
111.66.228.0/22 No ROA Nonecovered by 111.66.224.0/19 673 100% 67
111.66.232.0/22 No ROA Other origin onlycovered by 111.66.224.0/19 673 100% 67
111.66.236.0/22 No ROA Nonecovered by 111.66.224.0/19 673 100% 67
111.66.240.0/22 No ROA Nonecovered by 111.66.224.0/19 673 100% 67
111.66.244.0/22 No ROA Other origin onlycovered by 111.66.224.0/19 673 100% 67
111.66.248.0/22 No ROA Nonecovered by 111.66.224.0/19 673 100% 67
111.66.252.0/22 No ROA Nonecovered by 111.66.224.0/19 673 100% 67
211.169.28.0/24 No ROA None 673 100% 67

AS-SET

AS45964 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 23 are in fix.csv.

  • ROA: none9
  • Route object: none9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none111.66.224.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.224.0/22Route objects for it name AS17718. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.228.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.228.0/22No route object for it. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.232.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.232.0/22Route objects for it name AS17718. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.236.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.236.0/22No route object for it. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.240.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.240.0/22No route object for it. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.244.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.244.0/22Route objects for it name AS17718. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.248.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.248.0/22No route object for it. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none111.66.252.0/22No ROA covers it. Add a ROA for AS45964, maxLength 22.673 of 673
Route object: none111.66.252.0/22No route object for it. A route object for 111.66.224.0/19 with origin AS45964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45964 in the RIR database for the space.673 of 673
ROA: none211.169.28.0/24No ROA covers it. Add a ROA for AS45964, maxLength 24.673 of 673
Route object: none211.169.28.0/24No route object for it. Add a route object with origin AS45964 in the RIR database for the space.673 of 673

Route objects not announced

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

1.247.16.0/24RADBNo ROA
111.66.224.0/19RADBNo ROA
124.0.17.44/30RADBNo ROA
180.80.49.0/24RADBNo ROA
180.80.50.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.