Data as of Nov 14, 2026

46.61.138.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
98% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.6K observations
  • Residential
  • Business

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • Shifter
  • StrikeProxy
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.61.0.0/16
since Sep 2018
AS12389Residential13,740
116 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.61.0.0/1665,536RU-RTK-20101022PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 30, 2011abuse@rt.ru
└ 46.61.138.0/304Daichi_VladivostokTicket 09-24788ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.4/304ONeryungrinskiy_gorodskoy_vodokanalTicket 10-36002ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.8/298TandemTicket 10-36704ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.16/2816DDG-2Ticket 10-19309ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.32/2816Informatsionnyy_tsentr_YakutiyaTicket 10-35421ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.48/298Amurskiy_gidrometallurgicheskiy_kombinatTicket 10-23611ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.56/304SokolovTicket 10-35602ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.60/304Yakutskiy_kolledzh_potrebitelskoy_kooperatsiiTicket 10-07713ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.64/2816DDG-2Ticket 10-20442ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.80/2816Rynok_Khabarovsk_2Ticket 10-28235ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.96/298Chudesnaya_stranaTicket 10-36543ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.104/298RodStor_DVFTicket 10-36114ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.112/2816Royal_Kredit_bank_DVFTicket 10-38567ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.128/2816Gorodok_BlagoveshchenskTicket 10-35195ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.144/298Novaya_volna_sinemaTicket 10-13367ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.152/298DDG-2Ticket 10-39584ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.160/2816Regionalnye_Tsifrovye_setiTicket 10-39110ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.176/298UFNS_Rossii_YakutiyaTicket 10-37782ASSIGNED PAJan 18, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.184/304Progress-88Ticket 10-39021ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.188/304Kontrolnoe_upravlenie_YakutiyaTicket 10-29031ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.192/2816Pravitelstvo_Khabarovskogo_krayaTicket 10-24901ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.208 - 46.61.138.21912Vostok-MediaTicket 10-39096ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.224/2816Russkaya_strakhovaya_transportnaya_kompaniyaTicket 10-39631ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.138.240/2816Upravlenie_Ministerstva_yustitsii_RF_po_PKTicket 11-00653ASSIGNED PAJan 19, 2011abuse@rt.ru
via RU-RTK-20101022

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

256 addresses
TypeAddressesShareRanges
Business25298%24
Residential41.6%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

46.61.128.0/17

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
Dec 2010 · 16 yr
Origin networks
1