Data as of Nov 16, 2026

62.217.176.0/21

11 residential-proxy exits · 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
11
0.54% of its addresses · 30 days
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

264 observations

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
62.217.176.0/24
since Jun 2022
AS198610HostingBeget LLC
62.217.177.0/24
since Jun 2022
AS198610HostingBeget LLC
62.217.178.0/24
since Sep 2022
AS198610HostingBeget LLC
62.217.179.0/24
since Sep 2022
AS198610HostingBeget LLC
62.217.180.0/24
since Dec 2022
AS198610HostingBeget LLC
62.217.181.0/24
since Jan 2023
AS198610HostingBeget LLC
62.217.182.0/24
since Jan 2023
AS198610HostingBeget LLC
62.217.183.0/24
since Jan 2023
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
62.217.176.0/212,048RU-BEGET-20020410Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PASep 25, 2020abuse@beget.ru
└ 62.217.176.0/24256BEGET-NET-106unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.177.0/24256BEGET-NET-107unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.178.0/24256BEGET-NET-108unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.179.0/24256BEGET-NET-109unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.180.0/24256BEGET-NET-110unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.181.0/24256BEGET-NET-111unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.182.0/24256BEGET-NET-112unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410
└ 62.217.183.0/24256BEGET-NET-113unknownASSIGNED PAOct 12, 2020abuse@beget.ru
via RU-BEGET-20020410

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
Aug 2023 · 3.3 yr
Origin networks
1