bgpreport

Network · data from 2026-11-12

AS13700 NEXUSWAVE - NexusWave

Registry name: NEXUSWAVE - NexusWave, US · not in PeeringDB

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

Announced routes

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

198.87.102.0/23 Valid None 673 100% 67
168.143.96.0/24 Valid None 672 100% 66
168.143.111.0/24 Valid None 672 100% 66
192.220.252.0/23 Valid None 666 99% 67
198.173.162.0/23 Valid None 665 99% 66
192.204.14.0/23 Valid None 664 99% 67
192.204.26.0/23 Valid Other IRR onlyNTTCOM 670 100% 66
79.182.236.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.182.239.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.182.248.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.182.249.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.182.186.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
79.182.187.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
79.182.204.0/24 Valid RIR databaseRADB, RIPE 32 5%low visibility 26
79.182.224.0/24 Valid RIR databaseRADB, RIPE 32 5%low visibility 26

AS-SET

AS13700 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 46 are in fix.csv.

  • Route object: none6
  • Route object: RIR1
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
Route object: none198.87.102.0/23No route object for it. Add a route object with origin AS13700 in the RIR database for the space.673 of 673
Route object: none168.143.96.0/24No route object for it. Add a route object with origin AS13700 in the RIR database for the space.672 of 673
Route object: none168.143.111.0/24No route object for it. Add a route object with origin AS13700 in the RIR database for the space.672 of 673
Route object: none192.220.252.0/23No route object for it. Add a route object with origin AS13700 in the RIR database for the space.666 of 673
Route object: none198.173.162.0/23No route object for it. Add a route object with origin AS13700 in the RIR database for the space.665 of 673
Route object: none192.204.14.0/23No route object for it. Add a route object with origin AS13700 in the RIR database for the space.664 of 673
Route object: RIR192.204.26.0/23Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

128.121.44.0/23NTTCOMValid
128.242.88.0/22NTTCOMValid
130.94.240.0/22NTTCOMValid
131.103.28.0/23NTTCOMValid
165.254.50.0/23NTTCOMValid
165.254.208.0/23NTTCOMValid
165.254.212.0/23NTTCOMValid
198.63.248.0/22NTTCOMValid
198.87.184.0/22NTTCOMValid
198.88.122.0/23NTTCOMValid
198.88.218.0/23NTTCOMValid
198.138.208.0/23NTTCOMValid
198.139.134.0/23NTTCOMValid
198.170.186.0/23NTTCOMValid
198.170.200.0/21NTTCOMValid
199.4.108.0/23NTTCOMValid
199.224.2.0/23NTTCOMValid
204.2.62.0/23NTTCOMValid
204.143.62.0/23NTTCOMValid
204.170.32.0/23NTTCOMValid
204.171.62.0/23NTTCOMValid
207.152.64.0/23NTTCOMValid
207.152.100.0/23NTTCOMValid
207.152.108.0/23NTTCOMValid
209.39.16.0/23NTTCOMValid
209.39.22.0/23NTTCOMValid
209.39.28.0/23NTTCOMValid
209.57.34.0/23NTTCOMValid
209.57.36.0/22NTTCOMValid
209.70.242.0/23NTTCOMValid
209.107.64.0/23NTTCOMValid
209.107.68.0/23NTTCOMValid
209.107.76.0/23NTTCOMValid
209.212.230.0/23NTTCOMValid
209.212.238.0/23NTTCOMValid
209.227.28.0/22NTTCOMValid
216.42.128.0/23NTTCOMValid
216.42.134.0/23NTTCOMValid
216.44.52.0/23NTTCOMValid

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.