Data as of Nov 13, 2026

80.252.16.0/22

8 residential-proxy exits · 30 days

LLC Global Telecom Co

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

147 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • FastProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • LudaxProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RapidProxy
  • SwiftProxy
  • 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
80.252.16.0/204,096RU-GLOBAL-20051122LLC Global Telecom Co (ORG-CGTC1-RIPE) · RUALLOCATED PANov 22, 2005abuse@global63.ru
└ 80.252.16.0/2664GLOBAL63RU-NETBackbone networkASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.16.64/2732GLOBAL63RU-NETPeripheral gatewaysASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.16.96/2732GLOBAL63RU-NETPeripheral gatewaysASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.16.128/25128GLOBAL63RU-NETServer farm/colocation LANASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.17.0/24256GLOBAL63RU-NETCustomers NetworksASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.18.0/24256GLOBAL63RU-NETCustomers NetworksASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122
└ 80.252.19.0/24256GLOBAL63RU-NETCustomers NetworksASSIGNED PANov 22, 2005abuse@global63.ru
via RU-GLOBAL-20051122

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
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1