bgpreport

Network · data from 2026-11-12

AS33481 BELWAVE COMMUNICATIONS

Registry name: BELWAVE-COMMUNICATIONS - BELWAVE COMMUNICATIONS, INC., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33481, 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.
216.171.240.0/20 No ROA None 673 100% 67
216.171.242.0/23 No ROA None 673 100% 67
216.171.246.0/23 No ROA None 673 100% 67
216.171.252.0/22 No ROA None 673 100% 67
216.195.96.0/19 No ROA None 673 100% 67
2605:ac80::/32 No ROA None 635 100% 67
216.195.126.0/24 No ROA None 2 0%low visibility 3
64.125.160.0/21 Valid None 673 100% 67

AS-SET

AS33481'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: none7
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none216.171.240.0/20No ROA covers it. Add a ROA for AS33481, maxLength 20.673 of 673
Route object: none216.171.240.0/20No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673
ROA: none216.171.242.0/23No ROA covers it. Add a ROA for AS33481, maxLength 23.673 of 673
Route object: none216.171.242.0/23No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673
ROA: none216.171.246.0/23No ROA covers it. Add a ROA for AS33481, maxLength 23.673 of 673
Route object: none216.171.246.0/23No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673
ROA: none216.171.252.0/22No ROA covers it. Add a ROA for AS33481, maxLength 22.673 of 673
Route object: none216.171.252.0/22No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673
ROA: none216.195.96.0/19No ROA covers it. Add a ROA for AS33481, maxLength 19.673 of 673
Route object: none216.195.96.0/19No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673
ROA: none2605:ac80::/32No ROA covers it. Add a ROA for AS33481, maxLength 32.635 of 636
Route object: none2605:ac80::/32No route object for it. Add a route object with origin AS33481 in the RIR database for the space.635 of 636
ROA: none216.195.126.0/24No ROA covers it. Add a ROA for AS33481, maxLength 24.2 of 673
Route object: none216.195.126.0/24No route object for it. Add a route object with origin AS33481 in the RIR database for the space.2 of 673
Route object: none64.125.160.0/21No route object for it. Add a route object with origin AS33481 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS33481 is announced.

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.