bgpreport

Network · data from 2026-11-12

AS19790 ASPIRE-FIBER - Aspire Broadband, LLC

Registry name: ASPIRE-FIBER - Aspire Broadband, LLC, US · not in PeeringDB

6IPv4 routes 83.3% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS19790, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS19790, 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.
131.239.58.0/24 No ROA RIR databaseARIN 672 100% 67
104.204.160.0/21 Valid Nonecovered by 104.204.160.0/20 672 100% 67
104.204.168.0/21 Valid Nonecovered by 104.204.160.0/20 672 100% 67
104.204.160.0/20 Valid RIR databaseARIN, RADB 673 100% 67
23.148.36.0/24 Valid RIR databaseARIN, RADB 672 100% 67
134.49.144.0/20 Valid RIR databaseARIN 672 100% 67
2602:f587::/36 Valid RIR databaseARIN, RADB 634 100% 68

AS-SET

AS19790 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none131.239.58.0/24No ROA covers it. Add a ROA for AS19790, maxLength 24.672 of 673
Route object: none104.204.160.0/21No route object for it. A route object for 104.204.160.0/20 with origin AS19790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19790 in the RIR database for the space.672 of 673
Route object: none104.204.168.0/21No route object for it. A route object for 104.204.160.0/20 with origin AS19790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19790 in the RIR database for the space.672 of 673

Route objects not announced

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

192.40.30.0/23RADBNo 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.