bgpreport

Network · data from 2026-11-12

AS30097 NuWave Communications

Registry name: NUWAVE - NuWave, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30097, 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.
74.119.8.0/23 Valid Nonecovered by 74.119.8.0/22 673 100% 67
204.10.92.0/23 Valid Nonecovered by 204.10.92.0/22 673 100% 67
199.87.45.0/24 Valid Other IRR onlyRADB 673 100% 67
199.87.46.0/24 Valid Other IRR onlyRADB 673 100% 67
199.87.47.0/24 Valid Other IRR onlyRADB 673 100% 67
204.10.94.0/24 Valid Other IRR onlyRADB 673 100% 67
204.10.95.0/24 Valid Other IRR onlyRADB 673 100% 67
74.119.11.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS30097'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 19 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none74.119.8.0/23No route object for it. A route object for 74.119.8.0/22 with origin AS30097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30097 in the RIR database for the space.673 of 673
Route object: none204.10.92.0/23No route object for it. A route object for 204.10.92.0/22 with origin AS30097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30097 in the RIR database for the space.673 of 673
Route object: RIR199.87.45.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR199.87.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR199.87.47.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.10.94.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.10.95.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.119.11.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

8.28.121.0/24RADBNo ROA
66.178.128.0/19RADBNo ROA
74.119.8.0/22ARIN, RADBValid
74.119.8.0/24RADBValid
74.119.9.0/24RADBValid
74.119.10.0/24RADBValid
199.87.44.0/22RADBValid
199.87.44.0/24RADBValid
204.10.92.0/22RADBValid
204.10.92.0/24RADBValid
204.10.93.0/24RADBValid

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.