bgpreport

Network · data from 2026-11-12

AS394752 AVATIVE-FIBER - Avative Fiber

Registry name: AVATIVE-FIBER - Avative Fiber, US · not in PeeringDB

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

Announced routes

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

23.134.156.0/24 No ROA Other origin only 671 100% 68
66.118.44.0/22 No ROA RIR databaseARIN 671 100% 68
104.152.80.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
136.175.96.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
161.13.160.0/20 No ROA RIR databaseARIN 671 100% 68
162.212.240.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
198.73.72.0/22 No ROA RIR databaseARIN 671 100% 68
2606:cb80::/32 No ROA RIR databaseARIN, RADB 634 100% 68

AS-SET

AS394752 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 14 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none23.134.156.0/24No ROA covers it. Add a ROA for AS394752, maxLength 24.671 of 673
Route object: none23.134.156.0/24Route objects for it name AS27165. Add a route object with origin AS394752 in the RIR database for the space.671 of 673
ROA: none66.118.44.0/22No ROA covers it. Add a ROA for AS394752, maxLength 22.671 of 673
ROA: none104.152.80.0/22No ROA covers it. Add a ROA for AS394752, maxLength 22.671 of 673
ROA: none136.175.96.0/22No ROA covers it. Add a ROA for AS394752, maxLength 22.671 of 673
ROA: none161.13.160.0/20No ROA covers it. Add a ROA for AS394752, maxLength 20.671 of 673
ROA: none162.212.240.0/22No ROA covers it. Add a ROA for AS394752, maxLength 22.671 of 673
ROA: none198.73.72.0/22No ROA covers it. Add a ROA for AS394752, maxLength 22.671 of 673
ROA: none2606:cb80::/32No ROA covers it. Add a ROA for AS394752, maxLength 32.634 of 636

Route objects not announced

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

23.157.96.0/24RADBNo ROA
66.248.245.0/24RADBNo ROA
67.22.61.0/24RADBNo ROA
108.165.36.0/22RADBNo ROA
2602:fe30::/36RADBNo 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.