bgpreport

Network · data from 2026-11-12

AS400110 ANUVU-AVI-01 - Anuvu Operations LLC

Registry name: ANUVU-AVI-01 - Anuvu Operations LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400110, 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.
184.169.46.0/23 No ROA None 673 100% 67
184.169.40.0/23 No ROA None 672 100% 67
184.169.38.0/23 No ROA None 671 100% 68
184.169.45.0/24 Valid RIR databaseARIN, RADB 673 100% 67
194.2.72.0/24 Valid RIR databaseRIPE 673 100% 67
184.169.30.0/23 Valid RIR databaseARIN, RADB 672 100% 67
184.169.42.0/23 Valid RIR databaseARIN, RADB 672 100% 67
184.169.42.0/24 Valid RIR databaseARIN, RADB 672 100% 67
184.169.43.0/24 Valid RIR databaseARIN, RADB 672 100% 67
184.169.44.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.140.64.0/18 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

AS400110 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: none3
  • Route object: none3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none184.169.46.0/23No ROA covers it. Add a ROA for AS400110, maxLength 23.673 of 673
Route object: none184.169.46.0/23No route object for it. Add a route object with origin AS400110 in the RIR database for the space.673 of 673
ROA: none184.169.40.0/23No ROA covers it. Add a ROA for AS400110, maxLength 23.672 of 673
Route object: none184.169.40.0/23No route object for it. Add a route object with origin AS400110 in the RIR database for the space.672 of 673
ROA: none184.169.38.0/23No ROA covers it. Add a ROA for AS400110, maxLength 23.671 of 673
Route object: none184.169.38.0/23No route object for it. Add a route object with origin AS400110 in the RIR database for the space.671 of 673

Route objects not announced

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

184.169.34.0/24ARIN, RADBValid
184.169.35.0/24ARIN, RADBValid
184.169.36.0/24ARIN, RADBValid
184.169.37.0/24ARIN, RADBValid
184.169.38.0/24ARIN, RADBValid
184.169.39.0/24ARIN, RADBValid
184.169.40.0/24ARIN, RADBValid
184.169.41.0/24ARIN, RADBValid
184.169.46.0/24ARIN, RADBValid
184.169.47.0/24ARIN, RADBValid

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.