LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

5.250.232.0/22

10 residential-proxy exits · 30 days

Fortex CJSC

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

Residential-proxy exits

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

Exits seen per day

3.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.250.233.0/2406
5.250.232.0/2405

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • Geonode
  • GhostConnect
  • HideProxy
  • IPFly
  • IPOasis
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • StrikeProxy
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.250.232.0/212,048RU-FORTEX-20120914Fortex CJSC (ORG-FC79-RIPE) · RUALLOCATED PASep 14, 2012mail@fortex.ru
└ 5.250.232.0/221,024RU-FORTEXunknownASSIGNED PAOct 18, 2018mail@fortex.ru
via RU-FORTEX-20120914

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 5.250.232.0/21

5.250.232.0/21

Routing history

Pattern
Stable
First seen
Nov 2012
Current origin since
Oct 2018 · 8.1 yr
Origin networks
2
Last change of origin
Oct 2018
Recorded history

History

Handoffs
1