Data as of Nov 20, 2026

81.200.112.0/21

No anonymizer space · no proxy exits in 30 days

Beget LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

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
81.200.112.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.113.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.114.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.115.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.116.0/24
since Mar 2017
AS198610HostingBeget LLC
81.200.117.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.118.0/24
since Jun 2016
AS198610HostingBeget LLC
81.200.119.0/24
since Jun 2016
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
81.200.112.0/212,048RU-BEGET-20060607Beget LLC (ORG-BL131-RIPE) · RUALLOCATED PAMay 12, 2016abuse@beget.ru
└ 81.200.112.0/24256BEGET-NET-28Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.113.0/24256BEGET-NET-29Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.114.0/24256BEGET-NET-30Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.115.0/24256BEGET-NET-31Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.116.0/24256BEGET-NET-32Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.117.0/24256BEGET-NET-33Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.118.0/24256BEGET-NET-34Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607
└ 81.200.119.0/24256BEGET-NET-35Beget LtdASSIGNED PAMay 25, 2016abuse@beget.ru
via RU-BEGET-20060607

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
Reactivated
First seen
Nov 2006
Current origin since
Jun 2022 · 4.4 yr
Origin networks
2
Last change of origin
Jun 2022
Recorded history

History

Handoffs
1