Home Prefix Lookup217.79.4.0/23

217.79.4.0/23 - ENEVA "Eneva" (AS200483)

IPv4RIPE NCCallocatedAS200483ENEVA-AS "Eneva" Ltd RPKI Valid

CIDR

217.79.4.0/23

IP Version

IPv4

Addresses

512

Mask

/23 (255.255.254.0)

Country

🇷🇺 Russia

City

Saint Petersburg

RIR

RIPE NCC

Status

allocated

Allocated

2009-02-06

Announced BGP Routes

1 of 1 route

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
217.79.4.0/23	AS200483 ENEVA-AS "Eneva" Ltd	Valid	RIPE	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
217.79.4.0/23	AS200483	/23	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS200483	RIPE	lir-ru-eneva-1-MNT	2026-03-16

Transfer History

Registry transfers of 217.79.4.0/23, blocks inside it, or blocks containing it.

217.79.4.0/23Transfer · 2026-02-27
"OBIT" Ltd.
🇷🇺 RU RIPE NCC
→
"Eneva" Ltd
🇷🇺 RU RIPE NCC

Date	Resource	From	To	Type
2026-02-27	217.79.4.0/23	"OBIT" Ltd. 🇷🇺 RU RIPE NCC	"Eneva" Ltd 🇷🇺 RU RIPE NCC	Transfer

Origin ASN

AS200483

ENEVA-AS "Eneva" Ltd

Related Prefixes

More prefixes of AS200483

All prefixes of AS200483 →

Geolocation

Country🇷🇺RussiaRU

CitySaint Petersburg

Abuse Contact

Learn more

RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
RPKI validatorCheck ROA coverage for any prefix or ASN
What is BGP?How prefixes are announced and routed
More-specific prefixesGlossary: covering and more-specific routes
IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently

API

Open

GEThttps://api.ipctl.io/v1/prefix/217.79.4.0/23

Returns prefix allocation, BGP routes, and more-specific subnets.

curl -s "https://api.ipctl.io/v1/prefix/217.79.4.0/23" | jq

External Links

RIPEstat