Data as of Nov 16, 2026

217.79.12.0/23

6 residential-proxy exits · 30 days

'OBIT' Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
43
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

402 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.79.13.0/2404
217.79.12.0/2402

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VibeProxies
  • 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
217.79.9.0 - 217.79.15.2551,792RU-OBIT-20090206"OBIT" Ltd. (ORG-OL12-RIPE) · RUALLOCATED PAFeb 27, 2026abuse@obit.ru
└ 217.79.12.0/24256VIPMK-LANVIPMK networkASSIGNED PAFeb 3, 2010abuse@obit.ru
via RU-OBIT-20090206
└ 217.79.13.0/24256VIPMK-LANVIPMK networkASSIGNED PAFeb 15, 2010abuse@obit.ru
via RU-OBIT-20090206

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 this prefix

Summary

Routing history

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