Network · data from 2026-11-12

AS3927 RGNET-IAD RGnet OU

Registry name: RGNET-IAD RGnet OU, EE · not in PeeringDB

1IPv4 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 AS3927, seen from no peer

Announced routes

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


2001:418:8006::/48	Valid	Other IRR onlyNTTCOM	635 100%	67
198.180.150.0/24	Valid	RIR databaseRIPE	673 100%	67

AS-SET

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

Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	2001:418:8006::/48	Route object only in NTTCOM. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

2001:418:8006::/48

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

635 of 636

Route objects not announced

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