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

46.231.210.0/24

5 residential-proxy exits · 30 days

'OBIT' Ltd.

Announcement
46.231.210.0/23
RPKI valid
Announced by
AS8492
Type
Business
94% of it

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

248 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.231.208.0/212,048RU-OBIT-20110208"OBIT" Ltd. (ORG-OL12-RIPE) · RUALLOCATED PAFeb 8, 2011abuse@obit.ru
└ 46.231.210.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20110208
└ 46.231.210.0/304RDN-LANRDN networkASSIGNED PAApr 11, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.8/304VVIU-LANVVIU networkASSIGNED PAApr 19, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.12/304SPATSIKO-LANSPATSIKO networkASSIGNED PAApr 15, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.16/304MELITTA-LANMELITTA networkASSIGNED PAApr 21, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.20/304GIDROSI-LANGIDROSI networkASSIGNED PAApr 13, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.24/304SKAT-LANSKAT networkASSIGNED PAApr 19, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.28/304FR-LANFR networkASSIGNED PAApr 13, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.32/2816STOPAVTO-LANSTOPAVTO networkASSIGNED PAApr 14, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.48/304TESLI-LANTESLI networkASSIGNED PAApr 14, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.52/304KG-LANKG networkASSIGNED PAApr 14, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.56/298VEKTOR-LANVEKTOR networkASSIGNED PAApr 13, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.64/298UDL-LANUDL networkASSIGNED PAOct 14, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.72/304ST-LANST networkASSIGNED PAApr 13, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.76/304PLAYINN-LANPLAYINN networkASSIGNED PAApr 18, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.80/298LI-LANLI networkASSIGNED PAApr 19, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.88/304ST-LANST networkASSIGNED PASep 23, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.96/304IAMI-LANIAMI networkASSIGNED PAApr 15, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.100/304FS-LANFS networkASSIGNED PAApr 26, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.104/298MBSERVIS-LANMBSERVIS networkASSIGNED PAApr 15, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.112/304PE-LANPE networkASSIGNED PAApr 22, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.116/304ST-LANST networkASSIGNED PAApr 20, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.120/304ETM-LANETM networkASSIGNED PAApr 28, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.124/304AIESTI-LANAIESTI networkASSIGNED PAApr 18, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.128/2816YUPITER-LANYUPITER networkASSIGNED PAApr 18, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.144/304MORGAL-LANMORGAL networkASSIGNED PAApr 29, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.148/304AVRORATUR-LANAVRORATUR networkASSIGNED PAApr 19, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.152/298ASKENT-LANASKENT networkASSIGNED PAJun 3, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.160/304LAN-LANLAN networkASSIGNED PAApr 20, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.164/304GARANTAVTO-LANGARANTAVTO networkASSIGNED PAApr 29, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.168/298ST-LANST networkASSIGNED PAMay 4, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.176/298ST-LANST networkASSIGNED PAJun 23, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.188/304SEZAR-LANSEZAR networkASSIGNED PAApr 25, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.192/298EFO-LANEFO networkASSIGNED PAJun 6, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.200/304NN-LANNN networkASSIGNED PAApr 26, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.204/304POZHSERVIS-LANPOZHSERVIS networkASSIGNED PAApr 21, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.208/304KVADRO-LANKVADRO networkASSIGNED PAMay 23, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.212/304ZHSV-LANZHSV networkASSIGNED PAApr 26, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.216/304MEDZHIKNEON-LANMEDZHIKNEON networkASSIGNED PAMay 4, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.220/304TDC-LANTDC networkASSIGNED PAApr 26, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.224/304AM-LANAM networkASSIGNED PAJun 8, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.228/304SGN-LANSGN networkASSIGNED PAApr 27, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.232/298TKDOM-LANTKDOM networkASSIGNED PAApr 22, 2011abuse@obit.ru
via OBIT-LAN
└ 46.231.210.240/2816SPAUIE-LANSPAUIE networkASSIGNED PAJul 19, 2011abuse@obit.ru
via OBIT-LAN

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
Business24094%42
Internet provider166.3%4

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 46.231.210.0/23

46.231.210.0/23

Routing history

Pattern
Stable
First seen
Jan 2014
Current origin since
Jan 2014 · 13 yr
Origin networks
1