bgpreport

Network · data from 2026-11-12

AS18812 NEWWAVECOMM - New Wave Communications

Registry name: NEWWAVECOMM - New Wave Communications, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18812, 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.
96.18.246.0/24 No ROA None 671 100% 67
98.142.60.0/24 No ROA None 671 100% 67

AS-SET

AS18812 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 35 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none96.18.246.0/24No ROA covers it. Add a ROA for AS18812, maxLength 24.671 of 673
Route object: none96.18.246.0/24No route object for it. Add a route object with origin AS18812 in the RIR database for the space.671 of 673
ROA: none98.142.60.0/24No ROA covers it. Add a ROA for AS18812, maxLength 24.671 of 673
Route object: none98.142.60.0/24No route object for it. Add a route object with origin AS18812 in the RIR database for the space.671 of 673

Route objects not announced

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

12.2.6.0/23RADBNo ROA
24.49.93.0/24RADBNo ROA
24.51.168.0/23RADBNo ROA
24.100.0.0/17ALTDB, RADBNo ROA
24.100.6.0/23RADBNo ROA
24.100.8.0/23RADBNo ROA
24.100.42.0/23RADBNo ROA
24.100.108.0/23RADBNo ROA
24.100.118.0/23RADBNo ROA
24.100.128.0/18RADBNo ROA
63.142.64.0/18RADBNo ROA
64.188.202.0/23RADBNo ROA
64.188.204.0/22RADBNo ROA
72.51.128.0/17RADBNo ROA
72.51.244.0/23RADBNo ROA
72.51.248.0/24RADBNo ROA
72.51.254.0/23RADBNo ROA
76.11.128.0/17RADBNo ROA
76.11.144.0/22RADBNo ROA
76.11.172.0/22RADBNo ROA
76.11.180.0/22RADBNo ROA
76.11.184.0/22RADBNo ROA
76.11.210.0/23RADBNo ROA
76.11.214.0/23RADBNo ROA
76.11.228.0/22RADBNo ROA
76.11.238.0/23RADBNo ROA
206.81.204.0/22RADBNo ROA
206.81.208.0/23RADBNo ROA
209.97.64.0/19RADBNo ROA
209.97.86.0/23RADBNo ROA
209.97.90.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.