Data as of Nov 15, 2026

193.176.76.0/22

1 residential-proxy exit · 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

5 observations

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
193.176.76.0/24
since Oct 2018
AS198610HostingBeget LLC
193.176.77.0/24
since Oct 2018
AS198610HostingBeget LLC
193.176.78.0/24
since Oct 2018
AS198610HostingBeget LLC
193.176.79.0/24
since Oct 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
193.176.76.0/221,024RU-BEGET-20181025Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PAApr 6, 2022abuse@beget.ru
└ 193.176.76.0/24256BEGET-NET-44unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181025
└ 193.176.77.0/24256BEGET-NET-45unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181025
└ 193.176.78.0/24256BEGET-NET-46unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181025
└ 193.176.79.0/24256BEGET-NET-47unknownASSIGNED PAOct 8, 2019abuse@beget.ru
via RU-BEGET-20181025

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