Data as of Nov 10, 2026

185.78.28.0/22

2 residential-proxy exits · 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

172 observations

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
185.78.28.0/24
since Dec 2014
AS198610HostingBeget LLC
185.78.29.0/24
since Dec 2014
AS198610HostingBeget LLC
185.78.30.0/24
since Dec 2014
AS198610HostingBeget LLC
185.78.31.0/24
since Dec 2014
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
185.78.28.0/221,024RU-BEGET-20141121Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PANov 27, 2014abuse@beget.ru
└ 185.78.28.0/24256BEGET-NET16Hosting serversASSIGNED PAFeb 9, 2015abuse@beget.ru
via RU-BEGET-20141121
└ 185.78.29.0/24256BEGET-NET17Hosting serversASSIGNED PAFeb 9, 2015abuse@beget.ru
via RU-BEGET-20141121
└ 185.78.30.0/24256BEGET-NET18Hosting serversASSIGNED PAFeb 9, 2015abuse@beget.ru
via RU-BEGET-20141121
└ 185.78.31.0/24256BEGET-NET19Hosting serversASSIGNED PAFeb 9, 2015abuse@beget.ru
via RU-BEGET-20141121

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
Dec 2014
Current origin since
Jun 2022 · 4.4 yr
Origin networks
1