Data as of Nov 10, 2026

46.48.26.0/24

13 residential-proxy exits · 30 days

LLC 'KomTehCentr'

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
13
5.1% of its addresses · 30 days
Always-on exits
3
23% of its exits
Providers
45
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.48.0.0/1732,768RU-KTC-20100622LLC "KomTehCentr" (ORG-EP3-RIPE) · RUALLOCATED PAJun 22, 2010noc@itmh.ru
└ 46.48.24.0/221,024MIRALOGIC-NETLLC KOMTEHCENTR FTTB CustomersASSIGNED PASep 18, 2017noc@itmh.ru
via RU-KTC-20100622

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 46.48.0.0/17

46.48.0.0/17

Routing history

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