ResearchRouting table, RPKI, IRR & looking glass

AS3927 RGnet OU

AS3927 (RGNET-IAD) is registered to RGnet OU in EE, through RIPE. It originates 2 prefixes in the global routing table.

1
IPv4 prefixes
1
IPv6 prefixes
256
IPv4 addresses
100%
RPKI valid

Who holds AS3927

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS3927
Handle
RGNET-IAD
Organization
RGnet OU
Country
EE
Registry
RIPE
ASPA
None published
WHOIS recordRIPE
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to 'AS3927 - AS3927'

as-block:       AS3927 - AS3927
descr:          RIPE NCC ASN block
remarks:        These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by:         RIPE-NCC-HM-MNT
created:        2019-06-17T14:41:50Z
last-modified:  2019-06-17T14:41:50Z
source:         RIPE

% Information related to 'AS3927'

% Abuse contact for 'AS3927' is 'blackhole@bogus.com'

aut-num:        AS3927
as-name:        RGNET-IAD
descr:          RGnet Ashburn DC2
org:            ORG-RO47-RIPE
admin-c:        RB366-ARIN
tech-c:         RB366-ARIN
abuse-c:        AR52766-RIPE
import:         from AS2914 accept ANY
export:         to AS2914 announce AS3927
import:         from AS174 accept ANY
export:         to AS174 announce AS3927
import:         from AS19940 accept AS19940
export:         to AS19940 announce ANY
import:         from AS198794 accept AS198794
export:         to AS198794 announce NOT ANY
import:         from AS10233 accept AS10233
export:         to AS10233 announce NOT ANY
admin-c:        RB45695-RIPE
tech-c:         RB45695-RIPE
status:         LEGACY
mnt-by:         MAINT-RGNET
mnt-by:         RIPE-NCC-LEGACY-MNT
created:        2002-08-11T20:35:57Z
last-modified:  2025-03-31T21:37:53Z
source:         RIPE # Filtered

organisation:   ORG-RO47-RIPE
org-name:       RGnet OU
country:        EE
reg-nr:         14715872
org-type:       LIR
address:        Sakala tn 7-2
address:        EE-10141
address:        Tallinn
address:        ESTONIA
phone:          +1 206 356 8341
admin-c:        RB45695-RIPE
tech-c:         RB45695-RIPE
abuse-c:        AR52766-RIPE
mnt-ref:        MAINT-RGNET
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         MAINT-RGNET
created:        2019-05-20T12:22:32Z
last-modified:  2026-05-13T07:04:26Z
source:         RIPE # Filtered

person:         Randy Bush
address:        RGnet, LLC
address:        5147 Crystal Springs
address:        Bainbridge Island, WA 98110
address:        United States
phone:          +1 206 356 8341
fax-no:         +1 206 973 2762
nic-hdl:        RB366-ARIN
mnt-by:         MAINT-RGNET
created:        1970-01-01T00:00:00Z
last-modified:  2019-12-12T06:03:49Z
source:         RIPE # Filtered

person:         Randy Bush
address:        RGnet OÜ
address:        Sakala tn 7-2
address:        Tallinn
address:        EE-10141
address:        Estonia
phone:          +1 206 356 8341
nic-hdl:        RB45695-RIPE
mnt-by:         MAINT-RGNET
created:        2019-05-20T12:22:32Z
last-modified:  2024-07-06T16:08:10Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.124.1 (BUSA)


What AS3927 announces

Prefixes originated by AS3927 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
1
IPv6 prefixes
1
IPv4 addresses
256 (1 /24s)
RPKI valid
2 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS3927
2
With an IRR route object
2 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (1)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS3927 is reached through

The AS just before AS3927 in the paths our looking glass collectors hold, for 2 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPERGNET-IADMAINT-RGNET, RIPE-NCC-LEGACY-MNT

Route objects with origin AS3927: NTTCOM 1 · RIPE 1

as-sets that list AS3927 (2)