Data as of Nov 18, 2026

69.17.224.0/20

39 residential-proxy exits · 30 days

Frontier Networks Inc · space held by VIF Internet

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

Residential-proxy exits

Proxy exits
39
0.95% of its addresses · 30 days
Always-on exits
4
10% of its exits
Spread
14 of 16
/24s with at least one exit
Providers
85
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

22K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • HELODATA
  • IP2WORLD
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NSTPROXY_LITE
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • 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
69.17.224.0/198,192VIF-BLK-2VIF Internet (VIF) · CADirect AllocationJan 9, 2006talal@vif.com
└ 69.17.224.0/2732VIF-BLK-69-17-224-0---69-17-224-31unknown———
└ 69.17.224.32 - 69.17.224.7140VIF-BLK-69-17-224-32---69-17-224-71unknown———
└ 69.17.224.72 - 69.17.224.10332VIF-BLK-69-17-224-72---69-17-224-103unknown———
└ 69.17.224.104 - 69.17.225.87240VIF-BLK-69-17-224-104---69-17-225-87unknown———
└ 69.17.225.88 - 69.17.225.14356VIF-BLK-69-17-225-88---69-17-225-143unknown———
└ 69.17.225.144 - 69.17.225.20764VIF-BLK-69-17-225-144---69-17-225-207unknown———
└ 69.17.225.208 - 69.17.226.2372VIF-BLK-69-17-225-208---69-17-226-23unknown———
└ 69.17.226.24 - 69.17.226.159136VIF-BLK-69-17-226-24---69-17-226-159unknown———
└ 69.17.226.160 - 69.17.226.23980VIF-BLK-69-17-226-160---69-17-226-239unknown———
└ 69.17.226.240 - 69.17.228.31304VIF-BLK-69-17-226-240---69-17-228-31unknown———
└ 69.17.228.32 - 69.17.228.11180VIF-BLK-69-17-228-32---69-17-228-111unknown———
└ 69.17.228.112 - 69.17.228.13524VIF-BLK-69-17-228-112---69-17-228-135unknown———
└ 69.17.228.136 - 69.17.229.31152VIF-BLK-69-17-228-136---69-17-229-31unknown———
└ 69.17.229.32 - 69.17.229.12796VIF-BLK-69-17-229-32---69-17-229-127unknown———
└ 69.17.229.128/25128VIF-BLK-69-17-229-128---69-17-229-255unknown———
└ 69.17.230.0 - 69.17.231.79336VIF-BLK-69-17-230-0---69-17-231-79unknown———
└ 69.17.231.80 - 69.17.231.255176VIF-BLK-69-17-231-80---69-17-231-255unknown———
└ 69.17.232.0 - 69.17.233.95352VIF-BLK-69-17-232-0---69-17-233-95unknown———
└ 69.17.233.96 - 69.17.234.7168VIF-BLK-69-17-233-96---69-17-234-7unknown———
└ 69.17.234.8 - 69.17.234.143136VIF-BLK-69-17-234-8---69-17-234-143unknown———
└ 69.17.234.144 - 69.17.235.79192VIF-BLK-69-17-234-144---69-17-235-79unknown———
└ 69.17.235.80 - 69.17.235.191112VIF-BLK-69-17-235-80---69-17-235-191unknown———
└ 69.17.235.192 - 69.17.236.772VIF-BLK-69-17-235-192---69-17-236-7unknown———
└ 69.17.236.8 - 69.17.236.3124VIF-BLK-69-17-236-8---69-17-236-31unknown———
└ 69.17.236.32 - 69.17.236.207176VIF-BLK-69-17-236-32---69-17-236-207unknown———
└ 69.17.236.208 - 69.17.238.47352VIF-BLK-69-17-236-208---69-17-238-47unknown———

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Mar 2006
Current origin since
Jan 2025 · 1.8 yr
Origin networks
2
Last change of origin
Jan 2025
Recorded history

History

Handoffs
1