bgpreport

Network · data from 2026-11-12

AS46193 SKYWERX - Visionary Communications LLC

Registry name: SKYWERX - Visionary Communications LLC, US · not in PeeringDB

15IPv4 routes 93.3% RPKI valid · 86.7% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS46193, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46193, 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.
198.207.218.0/24 No ROA Other IRR onlyALTDB 670 100% 68
208.38.196.0/24 Valid None 670 100% 68
208.38.203.0/24 Valid None 670 100% 68
74.118.88.0/22 Valid Other IRR onlyRADB 670 100% 68
74.118.88.0/24 Valid Other IRR onlyRADB 670 100% 68
74.118.89.0/24 Valid Other IRR onlyRADB 670 100% 68
74.118.90.0/24 Valid Other IRR onlyRADB 670 100% 68
74.118.91.0/24 Valid Other IRR onlyRADB 670 100% 68
162.212.224.0/24 Valid Other IRR onlyRADB 670 100% 68
162.212.225.0/24 Valid Other IRR onlyRADB 670 100% 68
162.212.226.0/24 Valid Other IRR onlyRADB 670 100% 68
199.114.228.0/24 Valid Other IRR onlyRADB 670 100% 68
199.114.229.0/24 Valid Other IRR onlyRADB 670 100% 68
199.114.230.0/24 Valid Other IRR onlyRADB 670 100% 68
199.114.231.0/24 Valid Other IRR onlyRADB 670 100% 68

AS-SET

AS46193 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 16 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR13
ChangePrefix or setDetailFull-table peers
ROA: none198.207.218.0/24No ROA covers it. Add a ROA for AS46193, maxLength 24.670 of 673
Route object: RIR198.207.218.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: none208.38.196.0/24No route object for it. Add a route object with origin AS46193 in the RIR database for the space.670 of 673
Route object: none208.38.203.0/24No route object for it. Add a route object with origin AS46193 in the RIR database for the space.670 of 673
Route object: RIR74.118.88.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.118.88.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.118.89.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.118.90.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.118.91.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR162.212.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR162.212.225.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR162.212.226.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.114.228.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.114.229.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.114.230.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.114.231.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS46193 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.