bgpreport

Network · data from 2026-11-12

AS40069 AISNET - ASSURED INFORMATION SECURITY, INC.

Registry name: AISNET - ASSURED INFORMATION SECURITY, INC., US · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS40069, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40069, 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.
64.32.46.0/24 No ROA Nonecovered by 64.32.46.0/23 671 100% 67
2602:805:7000::/48 No ROA Nonecovered by 2602:805:7000::/44 635 100% 67
204.52.216.0/24 No ROA Other IRR onlyRADB 673 100% 67
64.32.46.0/23 No ROA RIR databaseARIN, RADB 672 100% 67
2602:805:7000::/44 No ROA RIR databaseARIN 634 100% 67

AS-SET

AS40069 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: none5
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none64.32.46.0/24No ROA covers it. Add a ROA for AS40069, maxLength 24.671 of 673
Route object: none64.32.46.0/24No route object for it. A route object for 64.32.46.0/23 with origin AS40069 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40069 in the RIR database for the space.671 of 673
ROA: none2602:805:7000::/48No ROA covers it. Add a ROA for AS40069, maxLength 48.635 of 636
Route object: none2602:805:7000::/48No route object for it. A route object for 2602:805:7000::/44 with origin AS40069 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40069 in the RIR database for the space.635 of 636
ROA: none204.52.216.0/24No ROA covers it. Add a ROA for AS40069, maxLength 24.673 of 673
Route object: RIR204.52.216.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none64.32.46.0/23No ROA covers it. Add a ROA for AS40069, maxLength 23.672 of 673
ROA: none2602:805:7000::/44No ROA covers it. Add a ROA for AS40069, maxLength 44.634 of 636

Route objects not announced

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