Network · data from 2026-11-12

AS23805 Watarase Television

Registry name: WATVnet - Watarase Television Co.,Ltd, JP · PeeringDB

5IPv4 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 AS23805, seen from no peer

Announced routes

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


27.100.48.0/20	Valid	Other IRR onlyJPIRR	671 100%	67
126.52.104.0/21	Valid	Other IRR onlyJPIRR	671 100%	67
202.76.192.0/19	Valid	Other IRR onlyJPIRR	671 100%	67
103.42.168.0/22	Valid	Other IRR onlyJPIRR, RADB	669 99%	67
219.100.80.0/22	Valid	Other IRR onlyJPIRR, RADB	669 99%	67
2405:fc80::/32	Valid	Other IRR onlyJPIRR	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS23805: AS-WATV. 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 (AS23805 isn't in the set, or no route object for AS23805 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.

Name	Database	ASNs	Sets	Route objects	AS23805 in it	Not covered
AS-WATV	JPIRR	1	1	6	Yes	0

Name

Database

ASNs

Sets

Route objects

AS23805 in it

Not covered

AS-WATV

JPIRR

Yes

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

Route object: RIR6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	27.100.48.0/20	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	126.52.104.0/21	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	202.76.192.0/19	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	103.42.168.0/22	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	219.100.80.0/22	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2405:fc80::/32	Route object only in JPIRR. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

27.100.48.0/20

Route object only in JPIRR. Add it in the RIR database for the space.

671 of 673

Route object: RIR

126.52.104.0/21

Route object only in JPIRR. Add it in the RIR database for the space.

671 of 673

Route object: RIR

202.76.192.0/19

Route object only in JPIRR. Add it in the RIR database for the space.

671 of 673

Route object: RIR

103.42.168.0/22

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

669 of 673

Route object: RIR

219.100.80.0/22

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

669 of 673

Route object: RIR

2405:fc80::/32

Route object only in JPIRR. Add it in the RIR database for the space.

634 of 636

Route objects not announced

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