Data as of Nov 16, 2026

95.214.60.0/22

3 residential-proxy exits · 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

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

Exits seen per day

355 observations

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
95.214.60.0/24
since Dec 2018
AS198610HostingBeget LLC
95.214.61.0/24
since Dec 2018
AS198610HostingBeget LLC
95.214.62.0/24
since Dec 2018
AS198610HostingBeget LLC
95.214.63.0/24
since Dec 2018
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
95.214.60.0/221,024RU-BEGET-20181221Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PAApr 6, 2022abuse@beget.ru
└ 95.214.60.0/24256BEGET-NET-48unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181221
└ 95.214.61.0/24256BEGET-NET-49unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181221
└ 95.214.62.0/321BEGET-NET-50unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181221
└ 95.214.62.1 - 95.214.62.255255BEGET-NET-50unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181221
└ 95.214.63.0/24256BEGET-NET-51unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181221

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