bgpreport

Network · data from 2026-11-12

AS54623 One Internet America AS54623

Registry name: ONE-INTERNET-AMERICA - One Internet America, LLC, US · PeeringDB

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

Announced routes

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

172.83.136.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
172.83.138.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
172.83.139.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
172.83.140.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
172.83.141.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
172.83.142.0/24 No ROA Nonecovered by 172.83.136.0/21 673 100% 67
8.23.241.0/24 No ROA None 672 100% 67
142.214.239.0/24 No ROA None 672 100% 67
38.91.105.0/24 No ROA Other origin only 671 100% 67
172.102.240.0/21 No ROA Other IRR onlyRADB 673 100% 67
23.166.128.0/24 No ROA RIR databaseARIN 673 100% 67
172.83.136.0/21 No ROA RIR databaseARIN, RADB 671 100% 67

AS-SET

AS54623's PeeringDB record names no 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: none12
  • Route object: none9
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none172.83.136.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.136.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none172.83.138.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.138.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none172.83.139.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.139.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none172.83.140.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.140.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none172.83.141.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.141.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none172.83.142.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
Route object: none172.83.142.0/24No route object for it. A route object for 172.83.136.0/21 with origin AS54623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54623 in the RIR database for the space.673 of 673
ROA: none8.23.241.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.672 of 673
Route object: none8.23.241.0/24No route object for it. Add a route object with origin AS54623 in the RIR database for the space.672 of 673
ROA: none142.214.239.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.672 of 673
Route object: none142.214.239.0/24No route object for it. Add a route object with origin AS54623 in the RIR database for the space.672 of 673
ROA: none38.91.105.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.671 of 673
Route object: none38.91.105.0/24Route objects for it name AS11123. Add a route object with origin AS54623 in the RIR database for the space.671 of 673
ROA: none172.102.240.0/21No ROA covers it. Add a ROA for AS54623, maxLength 21.673 of 673
Route object: RIR172.102.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none23.166.128.0/24No ROA covers it. Add a ROA for AS54623, maxLength 24.673 of 673
ROA: none172.83.136.0/21No ROA covers it. Add a ROA for AS54623, maxLength 21.671 of 673

Route objects not announced

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

2604:3340::/32ARINNo 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.