LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

46.255.96.0/21

1 residential-proxy exit · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS42358
Type
Residential
89% of it

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 8
/24s with at least one exit
Providers
20
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • StrikeProxy
  • Thordata

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.255.96.0/212,048RU-RTK-20101227PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 30, 2021abuse@rt.ru
└ 46.255.96.0/2816URALHIM-NETUralHim Network in Kirovo-ChepetskASSIGNED PAApr 20, 2012abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.16/298Lepse24-BC-NetLepseASSIGNED PAApr 20, 2012abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.24/298IPK-NETKirov Agriculture Specialists Advanced Training InstitutionASSIGNED PAJan 24, 2013abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.48/298AKO-Departments-NetSmall Customers on Karla Libknehta str. 69, KirovASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.56/298INSYS-ACCESS6-NETInSys infrastructure - access layer (/30 connections)ASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.64/2732VDS-CLI-NETVDS Clients in DC Pet24ASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.192/298MSCH52-NETFbuz "MSCH52" Fmba RussiaASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.96.200/298INSYS-SERVERS2InSys infrastructure - servers net 2ASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.97.0/2664leased-line-p2p-addr-46-255-97-0_26addr for leased line p2p linksASSIGNED PAJan 14, 2013abuse@rt.ru
via RU-RTK-20101227
└ 46.255.97.64/2732VSHU-NETFGBOU VPO Vyatka State University of HumanitiesASSIGNED PAMar 26, 2015abuse@rt.ru
via RU-RTK-20101227
└ 46.255.97.128/2816IHEAD-NETiHead company (ORG-IC89-RIPE)ASSIGNED PAApr 28, 2017abuse@ihead.ru
└ 46.255.97.144/2816IHEAD-NET2iHead company (ORG-IC89-RIPE)ASSIGNED PAJul 9, 2019abuse@ihead.ru
└ 46.255.98.0/23512pppoe-p2p-peer-addr-phizpppoe p2p addr for phiz usersASSIGNED PAJan 14, 2013abuse@rt.ru
via RU-RTK-20101227
└ 46.255.100.0/23512pppoe-p2p-peer-addr-jurpppoe p2p addr for jur usersASSIGNED PAJan 14, 2013abuse@rt.ru
via RU-RTK-20101227
└ 46.255.102.0/23512pppoe-p2p-peer-addr-phiz-no2pppoe p2p addr for phiz users net-no2ASSIGNED PAJan 14, 2013abuse@rt.ru
via RU-RTK-20101227

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential1,83289%6
Business20810%10
Hosting80.39%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Jan 2011 · 16 yr
Origin networks
1