Data as of Nov 14, 2026

95.161.238.0/24

2 residential-proxy exits · 30 days

'OBIT' Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
98% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
25
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

87 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
95.161.228.0 - 95.161.238.2552,816RU-OBIT-20081223"OBIT" Ltd. (ORG-OL12-RIPE) · RUALLOCATED PAMar 18, 2026abuse@obit.ru
└ 95.161.238.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20081223
└ 95.161.238.0/304ZNAMYATRUDA-LANZNAMYATRUDA networkASSIGNED PAAug 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.4/304TR-LANTR networkASSIGNED PAAug 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.8/304FOSTRANS-LANFOSTRANS networkASSIGNED PAAug 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.12/304DIOMA-LANDIOMA networkASSIGNED PAAug 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.16/304RESOLUT-LANRESOLUT networkASSIGNED PAAug 4, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.20/304UA-LANUA networkASSIGNED PAAug 4, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.24/304OZERKI-LANOZERKI networkASSIGNED PAAug 4, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.28/304BUSOMANIA-LANBUSOMANIA networkASSIGNED PAAug 4, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.32/304GALTOM-LANGALTOM networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.36/304CII-LANCII networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.40/304BILOGISTICS-LANBILOGISTICS networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.44/304TREIDKOSM-LANTREIDKOSM networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.48/304RTK-LANRTK networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.52/304SV-LANSV networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.56/304PR-LANPR networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.60/304KABVIKING-LANKABVIKING networkASSIGNED PAAug 5, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.64/304SMV-LANSMV networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.68/304VSESVOI-LANVSESVOI networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.72/304LEDA-LANLEDA networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.76/304STROITEL-LANSTROITEL networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.80/304LDS-LANLDS networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.84/304LDS-LANLDS networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.88/304TECHNOGRAD-LANTECHNOGRAD networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.92/304TECHNOGRAD-LANTECHNOGRAD networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.96/304TECHNOGRAD-LANTECHNOGRAD networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.100/304OLIMP-LANOLIMP networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.104/304OLIMP-LANOLIMP networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.108/304OLIMP-LANOLIMP networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.112/304OLIMP-LANOLIMP networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.116/304PETROSIR-LANPETROSIR networkASSIGNED PAAug 6, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.120/304RENEISSANS-LANRENEISSANS networkASSIGNED PAAug 7, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.124/304RENEISSANS-LANRENEISSANS networkASSIGNED PAAug 7, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.128/298METEOR-LANMETEOR networkASSIGNED PAAug 8, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.140/304UKPN-LANUKPN networkASSIGNED PAAug 20, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.144/298GRINSANDS-LANGRINSANDS networkASSIGNED PAAug 18, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.152/298BIGBOX-LANBIGBOX networkASSIGNED PAAug 18, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.160/2816ESENDKEI-LANESENDKEI networkASSIGNED PAAug 20, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.176/298CSP-LANCSP networkASSIGNED PAAug 20, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.184/298CSP-LANCSP networkASSIGNED PAAug 20, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.192/298MLSCHT-LANMLSCHT networkASSIGNED PAAug 28, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.200/298ULMART-LANULMART networkASSIGNED PASep 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.208/298PMS-CLASSIC-LANPMS-CLASSIC networkASSIGNED PASep 1, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.216/298TRANS-AERO-LANTRANS-AERO networkASSIGNED PASep 2, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.224/298PMS-CLASSIC-LANPMS-CLASSIC networkASSIGNED PASep 2, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.232/298PARFUM-LANPARFUM networkASSIGNED PASep 2, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.240/304PROFI-LANPROFI networkASSIGNED PASep 2, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.244/304OSTIN-LANOSTIN networkASSIGNED PASep 3, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.248/304PAPAGAL-LANPAPAGAL networkASSIGNED PASep 4, 2014abuse@obit.ru
via OBIT-LAN
└ 95.161.238.252/304DETI-LANDETI networkASSIGNED PASep 4, 2014abuse@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
Business25298%49
Internet provider41.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2026
Current origin since
Mar 2026 · 8 mo
Origin networks
1