Data as of Nov 12, 2026

31.28.0.0/19

134 residential-proxy exits · 30 days

Citytelecom LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
81% of it

Residential-proxy exits

Proxy exits
134
1.6% of its addresses · 30 days
Always-on exits
2
1.5% of its exits
Spread
16 of 32
/24s with at least one exit
Providers
95
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

7.0K observations
  • Residential
  • Unknown

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
31.28.3.0/24
since Apr 2025
AS28762HostingCitytelecom LLC
31.28.8.0/24
since Mar 2013
AS29076Residential11
1 always on
Citytelecom LLC
31.28.9.0/24
since Mar 2013
AS29076ResidentialCitytelecom LLC
31.28.10.0/24
since Mar 2013
AS29076Residential12Citytelecom LLC
31.28.11.0/24
since Mar 2013
AS29076Residential13Citytelecom LLC
31.28.12.0/24
since Oct 2023
AS29076Residential7Citytelecom LLC
31.28.14.0/23
since Oct 2023
AS29076Residential14Citytelecom LLC
31.28.20.0/24
since Jun 2015
AS29076ResidentialCitytelecom LLC
31.28.21.0/24
since Mar 2013
AS29076Residential2Citytelecom LLC
31.28.22.0/24
since Nov 2015
AS204039UnknownCitytelecom LLC
31.28.24.0/24
since Sep 2015
AS12616HostingCitytelecom LLC
31.28.25.0/24
since May 2019
AS3175HostingCitytelecom LLC
31.28.27.0/24
since Sep 2015
AS12616HostingCitytelecom LLC
31.28.28.0/24
since Nov 2018
AS204041Unknown3Citytelecom LLC
31.28.30.0/24
since Sep 2019
AS29076Residential7Citytelecom 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
31.28.0.0/198,192RU-CITYTELECOM1-20110210Citytelecom LLC (ORG-SO181-RIPE) · RUALLOCATED PAMar 14, 2023abuse@citytelecom.ru
└ 31.28.0.0/24256Filanco-NET31-0unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.1.0/24256Citytelecom-NET-31-1unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.2.0/24256Citytelecom-NET-31-2unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.3.0/24256FILANCO-NET-31-3Citytelecom LLC (ORG-SO181-RIPE) · RUASSIGNED PAOct 31, 2011abuse@citytelecom.ru
└ 31.28.4.0/24256FILANCO-NET-31-4unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.5.0/24256FILANCO-NET-31-5unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.6.0/24256FILANCO-NET-31-6unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.7.0/24256FILANCO-NET-31-7unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.8.0/24256FILANCO-NET-31-8unknownASSIGNED PAOct 5, 2011abuse@filanco.ru
└ 31.28.9.0/24256FILANCO-NET-31-9unknownASSIGNED PAOct 5, 2011abuse@filanco.ru
└ 31.28.10.0/24256FILANCO-NET-31-10unknownASSIGNED PAOct 5, 2011abuse@filanco.ru
└ 31.28.11.0/24256FILANCO-NET-31-11unknownASSIGNED PAOct 5, 2011abuse@filanco.ru
└ 31.28.12.0/221,024FILANCO-NET-31-12unknownASSIGNED PAMay 15, 2012abuse@filanco.ru
└ 31.28.16.0/24256FILANCO-NET-31-16unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.17.0/24256FILANCO-NET-31-17unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.18.0/24256FILANCO-NET-31-18Cloud-IX Saint-Petersburg networkASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.19.0/24256FILANCO-NET-31-19Cloud-IX Moscow networkASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.20.0/24256FILANCO-NET-31-20unknownASSIGNED PAOct 31, 2011abuse@filanco.ru
└ 31.28.21.0/24256FILANCO-NET-31-21unknownASSIGNED PAOct 31, 2011abuse@filanco.ru
└ 31.28.22.0/24256FILANCO-NET-31-22unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.23.0/24256FILANCO-NET-31-23unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.24.0/24256FILANCO-NET-31-24unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.25.0/24256FILANCO-NET-31-25unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.26.0/24256FILANCO-NET-31-26unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.27.0/24256FILANCO-NET-31-27unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.28.0/24256FILANCO-NET-31-28unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.29.0/24256FILANCO-NET-31-29Cloud-IX Ekatirinburg networkASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.30.0/24256FILANCO-NET-31-30unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210
└ 31.28.31.0/24256FILANCO-NET-31-31unknownASSIGNED PAOct 31, 2011abuse@citytelecom.ru
via RU-CITYTELECOM1-20110210

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

8,192 addresses
TypeAddressesShareRanges
Residential6,65681%17
Hosting1,02413%4
Unknown5126.3%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1