bgpreport

Network · data from 2026-11-12

AS29804 VALU-NET - Valu-Net LLC.

Registry name: VALU-NET - Valu-Net LLC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29804, 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.
173.207.188.0/22 No ROA Other IRR onlyALTDB 667 99% 67
172.103.64.0/21 No ROA RIR databaseARIN 669 99% 67
96.19.244.0/22 No ROA RIR databaseARIN 667 99% 67
161.38.220.0/22 No ROA RIR databaseARIN 667 99% 67
162.251.44.0/22 No ROA RIR databaseARIN 667 99% 67
192.133.248.0/23 No ROA RIR databaseARIN 667 99% 67
192.208.30.0/23 No ROA RIR databaseARIN 667 99% 67
198.204.204.0/22 No ROA RIR databaseARIN 667 99% 67
199.188.56.0/22 No ROA RIR databaseARIN 667 99% 67
204.9.180.0/22 No ROA RIR databaseARIN 667 99% 67
204.145.104.0/22 No ROA RIR databaseARIN 667 99% 67
208.68.252.0/22 No ROA RIR databaseARIN 667 99% 67
2607:6300::/32 No ROA RIR databaseARIN 635 100% 67

AS-SET

AS29804 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 15 are in fix.csv.

  • ROA: none13
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none173.207.188.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
Route object: RIR173.207.188.0/22Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none172.103.64.0/21No ROA covers it. Add a ROA for AS29804, maxLength 21.669 of 673
ROA: none96.19.244.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none161.38.220.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none162.251.44.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none192.133.248.0/23No ROA covers it. Add a ROA for AS29804, maxLength 23.667 of 673
ROA: none192.208.30.0/23No ROA covers it. Add a ROA for AS29804, maxLength 23.667 of 673
ROA: none198.204.204.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none199.188.56.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none204.9.180.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none204.145.104.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none208.68.252.0/22No ROA covers it. Add a ROA for AS29804, maxLength 22.667 of 673
ROA: none2607:6300::/32No ROA covers it. Add a ROA for AS29804, maxLength 32.635 of 636

Route objects not announced

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

168.75.212.0/23RADBNo 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.