bgpreport

Network · data from 2026-11-12

AS30247 Voonami, Inc.

Registry name: VOONAMI - Voonami, Inc., US · PeeringDB

13IPv4 routes 69.2% RPKI valid · 84.6% with a route object
7IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS30247, seen from no peer

Announced routes

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

38.92.4.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.92.6.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.92.5.0/24 No ROA Other IRR onlyRADB 672 100% 67
206.55.219.0/24 No ROA RIR databaseARIN 673 100% 67
66.33.0.0/22 Valid None 673 100% 67
83.223.39.0/24 Valid None 673 100% 67
67.158.48.0/24 Valid RIR databaseARIN 673 100% 67
69.24.143.0/24 Valid RIR databaseARIN 673 100% 67
69.167.48.0/20 Valid RIR databaseARIN 673 100% 67
162.220.208.0/22 Valid RIR databaseARIN 673 100% 67
199.119.84.0/22 Valid RIR databaseARIN 673 100% 67
199.192.164.0/22 Valid RIR databaseARIN 673 100% 67
208.97.48.0/20 Valid RIR databaseARIN 673 100% 67
2607:b80::/32 Valid RIR databaseARIN 635 100% 68
2607:b80:3::/48 Valid RIR databaseARIN 635 100% 68
2607:b80::/48 Valid RIR databaseARIN 634 100% 68
2607:b80:1::/48 Valid RIR databaseARIN 634 100% 68
2607:b80:2::/48 Valid RIR databaseARIN 634 100% 68
2607:b80:100::/40 Valid RIR databaseARIN 634 100% 68
2607:b80:200::/40 Valid RIR databaseARIN 634 100% 68

AS-SET

AS30247's PeeringDB record names no 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: none4
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none38.92.4.0/23No ROA covers it. Add a ROA for AS30247, maxLength 23.673 of 673
Route object: RIR38.92.4.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.92.6.0/23No ROA covers it. Add a ROA for AS30247, maxLength 23.673 of 673
Route object: RIR38.92.6.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.92.5.0/24No ROA covers it. Add a ROA for AS30247, maxLength 24.672 of 673
Route object: RIR38.92.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.55.219.0/24No ROA covers it. Add a ROA for AS30247, maxLength 24.673 of 673
Route object: none66.33.0.0/22No route object for it. Add a route object with origin AS30247 in the RIR database for the space.673 of 673
Route object: none83.223.39.0/24No route object for it. Add a route object with origin AS30247 in the RIR database for the space.673 of 673

Route objects not announced

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

23.140.156.0/24ARINValid
38.92.4.0/22RADBNo ROA
38.92.4.0/24RADBNo ROA
38.92.6.0/24RADBNo ROA
38.92.7.0/24RADBNo ROA
2602:f61b::/40ARINValid

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.