Network · data from 2026-11-12

AS63784 DIGItalGOjp

Registry name: GSS-NET - Digital Agency, JP · PeeringDB

10IPv4 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 AS63784, seen from no peer

Announced routes

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


166.119.192.0/21	Valid	Other IRR onlyJPIRR	671 100%	67
166.119.200.0/21	Valid	Other IRR onlyJPIRR	671 100%	67
166.119.208.0/21	Valid	Other IRR onlyJPIRR	671 100%	67
166.119.216.0/21	Valid	Other IRR onlyJPIRR	671 100%	67
166.119.224.0/24	Valid	Other IRR onlyJPIRR	670 100%	67
103.157.242.0/23	Valid	Other IRR onlyJPIRR	669 99%	67
103.157.242.0/24	Valid	Other IRR onlyJPIRR	669 99%	67
103.157.243.0/24	Valid	Other IRR onlyJPIRR	669 99%	67
166.119.225.0/24	Valid	Other IRR onlyJPIRR	669 99%	67
166.119.226.0/24	Valid	Other IRR onlyJPIRR	669 99%	67
2406:ab40::/28	Valid	Other IRR onlyJPIRR	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS63784: JPIRR::AS-DIGITALGOJP. 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 (AS63784 isn't in the set, or no route object for AS63784 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	AS63784 in it	Not covered
JPIRR::AS-DIGITALGOJP	JPIRR	1	1	11	Yes	0

Name

Database

ASNs

Sets

Route objects

AS63784 in it

Not covered

JPIRR::AS-DIGITALGOJP

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

Route object: RIR11

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	166.119.192.0/21	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	166.119.200.0/21	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	166.119.208.0/21	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	166.119.216.0/21	Route object only in JPIRR. Add it in the RIR database for the space.	671 of 673
Route object: RIR	166.119.224.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	670 of 673
Route object: RIR	103.157.242.0/23	Route object only in JPIRR. Add it in the RIR database for the space.	669 of 673
Route object: RIR	103.157.242.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	669 of 673
Route object: RIR	103.157.243.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	669 of 673
Route object: RIR	166.119.225.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	669 of 673
Route object: RIR	166.119.226.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2406:ab40::/28	Route object only in JPIRR. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

166.119.192.0/21