bgpreport

Network · data from 2026-11-12

AS401944 VORTEX WIRELESS INTERNET - Vortex Wireless Internet

Registry name: VORTEX WIRELESS INTERNET - Vortex Wireless Internet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401944, 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.
38.45.216.0/23 No ROA None 52 8%low visibility 31
38.45.216.0/24 No ROA None 52 8%low visibility 31
38.45.217.0/24 No ROA None 52 8%low visibility 31
66.187.241.0/24 Valid Nonecovered by 66.187.240.0/22 673 100% 67
169.128.123.0/24 Valid Nonecovered by 169.128.122.0/23 673 100% 67
66.187.240.0/22 Valid RIR databaseARIN 671 100% 67
169.128.122.0/23 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

AS401944 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 8 are in fix.csv.

  • ROA: none3
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none38.45.216.0/23No ROA covers it. Add a ROA for AS401944, maxLength 23.52 of 673
Route object: none38.45.216.0/23No route object for it. Add a route object with origin AS401944 in the RIR database for the space.52 of 673
ROA: none38.45.216.0/24No ROA covers it. Add a ROA for AS401944, maxLength 24.52 of 673
Route object: none38.45.216.0/24No route object for it. Add a route object with origin AS401944 in the RIR database for the space.52 of 673
ROA: none38.45.217.0/24No ROA covers it. Add a ROA for AS401944, maxLength 24.52 of 673
Route object: none38.45.217.0/24No route object for it. Add a route object with origin AS401944 in the RIR database for the space.52 of 673
Route object: none66.187.241.0/24No route object for it. A route object for 66.187.240.0/22 with origin AS401944 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401944 in the RIR database for the space.673 of 673
Route object: none169.128.123.0/24No route object for it. A route object for 169.128.122.0/23 with origin AS401944 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401944 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS401944 is announced.

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.