Data as of Nov 18, 2026

79.134.213.0/24

6 residential-proxy exits · 30 days

'OBIT' Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
42
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

337 observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • 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
79.134.200.0 - 79.134.221.2555,632RU-OBIT-20071022"OBIT" Ltd. (ORG-OL12-RIPE) · RUALLOCATED PAFeb 27, 2026abuse@obit.ru
└ 79.134.213.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20071022
└ 79.134.213.0/304PETROBALT-LANPETROBALT networkASSIGNED PAJul 30, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.4/304LDA-LANLDA networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.8/298ARZ-LANARZ networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.16/304LDA-LANLDA networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.20/304DETSKIIMIR-LANDETSKIIMIR networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.24/304TURIBA-LANTURIBA networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.28/304LAA-LANLAA networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.32/304KREDOINVEST-LANKREDOINVEST networkASSIGNED PAJul 31, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.36/304SKANDIRENT-LANSKANDIRENT networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.40/304TEPLOKOM-LANTEPLOKOM networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.44/304TAREAL-LANTAREAL networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.48/304BELUGA-LANBELUGA networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.52/304BALTIK-LANBALTIK networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.56/304MASTER-LANMASTER networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.60/304ARTDEKART-LANARTDEKART networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.64/304SPAR-LANSPAR networkASSIGNED PAAug 1, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.68/304ITSTRATEGIA-LANITSTRATEGIA networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.72/304URENHOLTS-LANURENHOLTS networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.76/304AZCHM-LANAZCHM networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.80/304SEVZAPGIPROZEM-LANSEVZAPGIPROZEM networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.84/304VSU-LANVSU networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.88/304TR-LANTR networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.92/304RITM-LANRITM networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.96/304RET-LANRET networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.100/304LENGO-LANLENGO networkASSIGNED PAAug 2, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.104/304BOKAR-LANBOKAR networkASSIGNED PAAug 5, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.108/304ANTRE-LANANTRE networkASSIGNED PAAug 5, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.112/304SOGAZ-LANSOGAZ networkASSIGNED PAAug 5, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.116/304KOMILFO-LANKOMILFO networkASSIGNED PAAug 5, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.120/304IT-LANIT networkASSIGNED PAAug 5, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.124/304EMK-LANEMK networkASSIGNED PAAug 6, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.128/304RESTO-LANRESTO networkASSIGNED PAAug 6, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.132/304NEVA-LANNEVA networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.136/298SKB-LANSKB networkASSIGNED PAAug 6, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.144/304ALFA-LANALFA networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.148/304ALFA-LANALFA networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.152/304UGRA-LANUGRA networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.156/304TELS-LANTELS networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.160/304BAN-LANBAN networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.164/304POLISTROI-LANPOLISTROI networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.168/304KIDERIA-LANKIDERIA networkASSIGNED PAAug 7, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.172/304EMK-LANEMK networkASSIGNED PAAug 8, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.176/304JNP-LANJNP networkASSIGNED PAAug 8, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.180/304DETI-LANDETI networkASSIGNED PAAug 8, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.184/304HKVMF-LANHKVMF networkASSIGNED PAAug 8, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.188/304FINSERVIS-LANFINSERVIS networkASSIGNED PAAug 9, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.192/304MATRIKS-LANMATRIKS networkASSIGNED PAAug 9, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.196/304RATSIONAL-LANRATSIONAL networkASSIGNED PAAug 9, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.200/304NII-LANNII networkASSIGNED PAAug 9, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.204/304ELDORADO-LANELDORADO networkASSIGNED PAAug 12, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.208/304ASFORMA-LANASFORMA networkASSIGNED PAAug 12, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.212/304CRT-LANCRT networkASSIGNED PAAug 12, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.216/304PIK-LANPIK networkASSIGNED PAAug 12, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.220/304LERI-LANLERI networkASSIGNED PAAug 12, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.224/304RIOMARKET-LANRIOMARKET networkASSIGNED PAAug 13, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.228/304DAR-LANDAR networkASSIGNED PAAug 13, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.232/304ALFABANK-LANALFABANK networkASSIGNED PAAug 13, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.236/304SKRIMER-LANSKRIMER networkASSIGNED PAAug 14, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.240/298FORT-LANFORT networkASSIGNED PAAug 13, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.248/304VKV-LANVKV networkASSIGNED PAAug 14, 2013abuse@obit.ru
via OBIT-LAN
└ 79.134.213.252/304TER-LANTER networkASSIGNED PAAug 14, 2013abuse@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.

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