bgpreport

Network · data from 2026-11-12

AS402390 WITL-US-AS - Wisewave

Registry name: WITL-US-AS - Wisewave, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402390, 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.
45.195.198.0/24 Invalid: origin RIR databaseAFRINIC 93 14% 44
156.236.12.0/24 Invalid: origin RIR databaseAFRINIC 60 9%low visibility 30
45.201.1.0/24 Invalid: origin RIR databaseAFRINIC 29 4%low visibility 22
82.39.145.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.39.195.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.124.145.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
104.166.73.0/24 Valid RIR databaseARIN, RADB 672 100% 67
108.186.236.0/24 Valid RIR databaseARIN, RADB 672 100% 67
151.241.40.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
151.244.166.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
172.82.186.0/24 Valid RIR databaseARIN, RADB 672 100% 67
141.11.238.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
151.244.223.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
193.31.112.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
154.197.66.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
151.240.253.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
178.95.22.0/24 Valid RIR databaseRADB, RIPE 659 98% 67

AS-SET

AS402390 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 4 are in fix.csv.

  • ROA: origin3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin45.195.198.0/24ROAs covering it name AS17561, not AS402390. If AS402390 should announce it, add a ROA for AS402390.93 of 673
ROA: origin156.236.12.0/24ROAs covering it name AS17561, not AS402390. If AS402390 should announce it, add a ROA for AS402390.60 of 673
ROA: origin45.201.1.0/24ROAs covering it name AS17561, not AS402390. If AS402390 should announce it, add a ROA for AS402390.29 of 673

Route objects not announced

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

156.252.82.0/24AFRINICInvalid: origin

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.