Data as of Nov 11, 2026

80.80.162.0/23

30 residential-proxy exits · 30 days

IPKO Telecommunications LLC

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
30
5.9% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

789 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.80.163.0/24024
80.80.162.0/2406

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • Datarama
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • IPCola
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.80.160.0/204,096AL-IPKO-20010717IPKO Telecommunications LLC (ORG-IA73-RIPE) · ALALLOCATED PA—abuse@ipko.com
└ 80.80.162.16/298IPKO-8080unknownASSIGNED PAMay 10, 2006abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.24/298IPKO-8080unknownASSIGNED PAApr 23, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.32/298IPKO-8080unknownASSIGNED PAApr 30, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.48/298IPKO-8080unknownASSIGNED PAMay 18, 2015abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.56/298IPKO-8080unknownASSIGNED PAApr 23, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.64 - 80.80.162.7512IPKO-8080unknownASSIGNED PAApr 23, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.80/2816IPKO-8080unknownASSIGNED PAMay 10, 2006abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.112/298IPKO-8080unknownASSIGNED PANov 15, 2006abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.162.128/25128IPKO-8080unknownASSIGNED PAMay 4, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.0/25128IPKO-8080unknownASSIGNED PAMay 4, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.128/298IPKO-8080unknownASSIGNED PAMay 18, 2015abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.136/298IPKO-8080unknownASSIGNED PANov 15, 2006abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.144/298IPKO-8080unknownASSIGNED PAMay 18, 2015abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.152/298IPKO-8080unknownASSIGNED PAMay 18, 2015abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.168/298IPKO-8080unknownASSIGNED PAApr 30, 2010abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.176/298IPKO-8080unknownASSIGNED PAMay 18, 2015abuse@ipko.com
via AL-IPKO-20010717
└ 80.80.163.192/2664IPKO-8080unknownASSIGNED PAMay 4, 2010abuse@ipko.com
via AL-IPKO-20010717

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 80.80.160.0/20

80.80.160.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1