Home ASN LookupAS3927

AS3927 RGNET-IAD RGnet OU

🇪🇪

Org handle: ORG-RO47-RIPE

RGnet Ashburn DC2

RIPE NCCallocated

Announced Prefixes (BGP)

2total

1 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)256

Announced (BGP)256

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇪🇪 EE

RIR

RIPE NCC

Status

allocated

Allocated

1994-10-12

Announced Prefixes

(BGP)2

Prefix	RPKI	IRR	Last Seen
198.180.150.0/24	Valid	RIPE	2026-10-11
2001:418:8006::/48	Valid	-	2026-10-11

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
198.180.150.0/24	🇪🇪 EE	RIPE	assigned

All 2 announced prefixes of AS3927 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

Networks AS3927 hands its own prefixes to: transit providers, or peers at an exchange.

AS174Cogent Communications1
AS2914NTT America1

Transfer History

Registry transfers of AS3927 between organisations.

AS3927inter-RIRTransfer · 2019-06-17
RGnet, LLC
🇺🇸 US ARIN
→
RGnet OU
🇳🇱 NL RIPE NCC

Date	Resource	From	To	Type
2019-06-17	AS3927inter-RIR	RGnet, LLC 🇺🇸 US ARIN	RGnet OU 🇳🇱 NL RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS3927 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/3927

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/3927" | jq