Data as of Nov 12, 2026

91.133.0.0/19

108 residential-proxy exits · 30 days

Fortex CJSC

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

Residential-proxy exits

Proxy exits
108
1.3% of its addresses · 30 days
Always-on exits
9
8.3% of its exits
Spread
16 of 32
/24s with at least one exit
Providers
73
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

17K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • LUMIPROXY
  • LemonPrime
  • LudaxProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • RainProxy
  • RoamProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • 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
91.133.0.0/198,192RU-FORTEX-20061030Fortex CJSC (ORG-FC79-RIPE) · RUALLOCATED PAJul 25, 2014mail@fortex.ru
└ 91.133.0.0/204,096FORTEX-NETunknownASSIGNED PAMar 16, 2018mail@fortex.ru
via RU-FORTEX-20061030
└ 91.133.16.0/204,096FORTEX-NETunknownASSIGNED PAMar 16, 2018mail@fortex.ru
via RU-FORTEX-20061030

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
Aug 2014
Current origin since
Aug 2014 · 12 yr
Origin networks
1