Data as of Nov 14, 2026

46.42.134.0/23

No anonymizer space · no proxy exits in 30 days

DataFort LLC · space held by PJSC "Vimpelcom"

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low
Recent change
New origin Oct 10, 2026
its first announcement on record

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.42.128.0/18
since Sep 2024
AS3216Residential2,543PJSC "Vimpelcom"

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
46.42.128.0/1816,384RU-SOVINTEL-20100805PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAAug 5, 2010abuse-b2b@beeline.ru
└ 46.42.128.0/198,192RU-BeeLine-et-TATINTEL-29042010BeeLine et TatIntelCom FTTB NetworkSUB-ALLOCATED PAJan 27, 2022abuse-b2b@beeline.ru
via RU-SOVINTEL-20100805
└ 46.42.128.0/204,096RU-BeeLine-B2B-clients-NET111250 Russia SOVINTEL/EDN et TatIntelSUB-ALLOCATED PAJan 28, 2022abuse-b2b@beeline.ru
via RU-BeeLine-et-TATINTEL-29042010
└ 46.42.134.0/23512RU-Vimpelcom-MSK-BeeCLOUD-Pool-NET111250 Russia Vimpelcom et SOVINTEL/EDNASSIGNED PAOct 16, 2026abuse-b2b@beeline.ru
via RU-BeeLine-B2B-clients-NET

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 10, 2026
Current origin since
Oct 10, 2026 · 1 mo
Origin networks
1