Data as of Nov 17, 2026

217.172.24.0/22

No anonymizer space · no proxy exits in 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
217.172.24.0/24
since Mar 2017
AS198610HostingBeget LLC
217.172.25.0/24
since Mar 2017
AS198610HostingBeget LLC
217.172.26.0/24
since Mar 2017
AS198610HostingBeget LLC
217.172.27.0/24
since Mar 2017
AS198610HostingBeget LLC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.172.24.0/221,024RU-BEGET-20040831Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PAMar 15, 2017abuse@beget.ru
└ 217.172.24.0/24256BEGET-NET-36unknownASSIGNED PAOct 4, 2019abuse@beget.ru
via RU-BEGET-20040831
└ 217.172.25.0/24256BEGET-NET-37unknownASSIGNED PAOct 4, 2019abuse@beget.ru
via RU-BEGET-20040831
└ 217.172.26.0/24256BEGET-NET-38unknownASSIGNED PAOct 4, 2019abuse@beget.ru
via RU-BEGET-20040831
└ 217.172.27.0/24256BEGET-NET-39unknownASSIGNED PAOct 4, 2019abuse@beget.ru
via RU-BEGET-20040831

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2022
Current origin since
Jun 2022 · 4.4 yr
Origin networks
1