bgpreport

Network · data from 2026-11-12

AS28098 AS28098 - ABGON COMUNICACIONES

Registry name: AS28098 - ABGON COMUNICACIONES, CL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28098, 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.231.48.0/22 No ROA Other origin only 668 99% 67
190.3.176.0/21 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
45.172.136.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.172.137.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.172.138.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.172.139.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.180.172.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.180.173.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.180.174.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.180.175.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
170.150.120.0/22 No ROA Other IRR onlyNTTCOM 668 99% 67
45.231.48.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
45.231.49.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
45.231.50.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
45.231.51.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
190.3.176.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.177.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.178.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.179.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.180.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.181.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.182.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.3.183.0/24 No ROA Other IRR onlyRADB 666 99% 67

AS-SET

AS28098 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 88 are in fix.csv.

  • ROA: none23
  • Route object: none1
  • Route object: RIR22
  • Route object: not announced42
ChangePrefix or setDetailFull-table peers
ROA: none45.231.48.0/22No ROA covers it. Add a ROA for AS28098, maxLength 22.668 of 673
Route object: none45.231.48.0/22Route objects for it name AS266724. Add a route object with origin AS28098 in the RIR database for the space.668 of 673
ROA: none190.3.176.0/21No ROA covers it. Add a ROA for AS28098, maxLength 21.669 of 673
Route object: RIR190.3.176.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.172.136.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.172.136.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.172.137.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.172.137.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.172.138.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.172.138.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.172.139.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.172.139.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.180.172.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.180.172.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.180.173.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.180.173.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.180.174.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.180.174.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.180.175.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.668 of 673
Route object: RIR45.180.175.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.150.120.0/22No ROA covers it. Add a ROA for AS28098, maxLength 22.668 of 673
Route object: RIR170.150.120.0/22Route object only in NTTCOM. Add it in the RIR database for the space.668 of 673
ROA: none45.231.48.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR45.231.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none45.231.49.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR45.231.49.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none45.231.50.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR45.231.50.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none45.231.51.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR45.231.51.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none190.3.176.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.176.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.177.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.177.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.178.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.178.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.179.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.179.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.180.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.180.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.181.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.181.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.182.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.667 of 673
Route object: RIR190.3.182.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.3.183.0/24No ROA covers it. Add a ROA for AS28098, maxLength 24.666 of 673
Route object: RIR190.3.183.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

45.65.160.0/22NTTCOMNo ROA
45.172.136.0/22RADBNo ROA
45.172.136.0/23RADBNo ROA
45.172.138.0/23RADBNo ROA
45.174.104.0/22RADBNo ROA
45.174.104.0/23RADBNo ROA
45.174.104.0/24NTTCOM, RADBNo ROA
45.174.105.0/24NTTCOM, RADBNo ROA
45.174.106.0/23RADBNo ROA
45.174.106.0/24NTTCOM, RADBNo ROA
45.174.107.0/24NTTCOM, RADBNo ROA
45.180.172.0/22RADBNo ROA
45.180.172.0/23RADBNo ROA
45.180.174.0/23RADBNo ROA
45.224.120.0/22NTTCOMNo ROA
45.225.80.0/22NTTCOMNo ROA
45.227.64.0/24NTTCOMNo ROA
45.227.65.0/24NTTCOMNo ROA
45.227.66.0/24NTTCOMNo ROA
45.227.67.0/24NTTCOMNo ROA
45.227.132.0/24NTTCOMNo ROA
45.227.133.0/24NTTCOMNo ROA
45.227.134.0/24NTTCOMNo ROA
45.227.135.0/24NTTCOMNo ROA
128.201.32.0/21NTTCOMNo ROA
181.191.176.0/22NTTCOMNo ROA
181.191.176.0/24NTTCOMNo ROA
181.191.177.0/24NTTCOMNo ROA
181.191.178.0/24NTTCOMNo ROA
181.191.179.0/24NTTCOMNo ROA
190.3.176.0/22RADBNo ROA
190.3.176.0/23RADBNo ROA
190.3.178.0/23RADBNo ROA
190.3.180.0/22RADBNo ROA
190.3.180.0/23RADBNo ROA
190.3.182.0/23RADBNo ROA
192.140.20.0/22NTTCOMNo ROA
192.141.212.0/22NTTCOMNo ROA
192.141.212.0/24NTTCOMNo ROA
192.141.213.0/24NTTCOMNo ROA
192.141.214.0/24NTTCOMNo ROA
192.141.215.0/24NTTCOMNo 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.