Data as of Nov 20, 2026

89.188.126.0/24

9 residential-proxy exits · 30 days

Citytelecom LLC

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
30
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.188.96.0/19
since May 2006
AS29076Residential144
6 always on
Citytelecom LLC

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
89.188.96.0/198,192RU-CITYTELECOM1-20060508Citytelecom LLC (ORG-SO181-RIPE) · RUALLOCATED PAMar 14, 2023abuse@citytelecom.ru
└ 89.188.126.0/24256FILANCO-NET-89-126unknownASSIGNED PAJan 13, 2020abuse@citytelecom.ru
via RU-CITYTELECOM1-20060508

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2013
Current origin since
Sep 2019 · 7.2 yr
Origin networks
1