Data as of Nov 13, 2026

178.16.157.0/24

7 residential-proxy exits · 30 days

OBIT-telecommunications, LLC

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
34
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.2K observations
  • Business
  • Internet provider

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

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
178.16.157.0/24256KZ-OBIT-TELECOMMUNICATION-20100303OBIT-telecommunications, LLC (ORG-OL282-RIPE) · KZALLOCATED PASep 6, 2023abuse@obit.kz
└ 178.16.157.0/298KFISHA-LANKFISHA networkASSIGNED PAApr 30, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.8/298RESMI-LANRESMI networkASSIGNED PAMay 17, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.16/304TTKA-LANTTKA networkASSIGNED PAAug 24, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.20/304PKMPITIUAILTD-LANPKMPITIUAILTD networkASSIGNED PAApr 15, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.24/304SOAEKK-LANSOAEKK networkASSIGNED PASep 1, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.28/304PT-LANPT networkASSIGNED PASep 7, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.32/2732MDK-LANMDK networkASSIGNED PAApr 30, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.64/298SDN-LANSDN networkASSIGNED PASep 28, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.76/304INVIVO-LANINVIVO networkASSIGNED PADec 13, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.80/2816PRIMA-LANPRIMA networkASSIGNED PAOct 14, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.96/2816BURGAN-LANBURGAN networkASSIGNED PAOct 5, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.112/304KAT-LANKAT networkASSIGNED PANov 18, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.120/304SDV-LANSDV networkASSIGNED PADec 14, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.124/304CDU-LANCDU networkASSIGNED PADec 21, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.132/304HCEL-LANHCEL networkASSIGNED PAJan 11, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.136/298TSK-LANTSK networkASSIGNED PAFeb 9, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.152/298CE-LANCE networkASSIGNED PANov 9, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.160/304PBIAG-LANPBIAG networkASSIGNED PAFeb 17, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.168/298YAKC-LANYAKC networkASSIGNED PAMar 11, 2011abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.176/2816GRUP4SEKURIKOR-LANGRUP4SEKURIKOR networkASSIGNED PAJan 23, 2012abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303
└ 178.16.157.192/2664ARLINE-LANARLINE networkASSIGNED PADec 23, 2010abuse@obit.kz
via KZ-OBIT-TELECOMMUNICATION-20100303

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
Business23291%21
Internet provider249.4%5

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2010
Current origin since
May 2010 · 17 yr
Origin networks
1