bgpreport

Network · data from 2026-11-12

AS37892 Cable media waiwai Co., Ltd.

Registry name: WAI-NET - Cable Media WAIWAI Co.,Ltd., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37892, 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.
124.247.0.0/17 Valid Other IRR onlyJPIRR, RADB 672 100% 67
124.247.128.0/18 Valid Other IRR onlyJPIRR, RADB 671 100% 67
202.145.20.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
202.145.26.0/23 Valid Other IRR onlyJPIRR, RADB 669 99% 67
202.145.28.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
202.220.6.0/23 Valid Other IRR onlyJPIRR, RADB 669 99% 67
2402:c840::/32 Valid Other IRR onlyJPIRR, RADB 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS37892: AS-WAINET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS37892 isn't in the set, or no route object for AS37892 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS37892 in itNot covered
AS-WAINET RADB1 member set in no database: AS37892:AS-TRANSIT 117 Yes 0
JPIRR (also)1 member set in no database: AS37892:AS-TRANSIT 117 Yes 0

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

  • Route object: RIR7
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: RIR124.247.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.247.128.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.145.20.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.145.26.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.145.28.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.220.6.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2402:c840::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberAS-WAINETAS-WAINET (RADB) lists AS37892:AS-TRANSIT; no IRR database read has it.

Route objects not announced

Every route object with origin AS37892 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.