Data as of Nov 16, 2026

93.92.200.0/21

46 residential-proxy exits · 30 days

Saint-Petersburg Computer Networks Ltd.

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

Residential-proxy exits

Proxy exits
46
2.2% of its addresses · 30 days
Always-on exits
14
30% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
82
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • HideProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LudaxProxy
  • Maskify
  • NSocks
  • NextProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXY_CC
  • PSBProxy
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_PREMIUM

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
93.92.200.0/212,048RU-SPBKS-20080206Saint-Petersburg Computer Networks Ltd. (ORG-SCNL3-RIPE) · RUALLOCATED PAFeb 6, 2008abuse@airnet.ru
└ 93.92.200.0/24256AIRNET-1unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.201.0/24256AIRNET-2unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.202.0/24256AIRNET-3unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.203.0/24256AIRNET-4unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.204.0/24256AIRNET-5unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.205.0/24256AIRNET-6unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.206.0/24256AIRNET-7unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206
└ 93.92.207.0/24256AIRNET-8unknownASSIGNED PAJul 15, 2021abuse@airnet.ru
via RU-SPBKS-20080206

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
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1