Data as of Nov 15, 2026

166.62.128.0/18

2 anonymizer addresses · 0.01% · VPN287 residential-proxy exits · 30 days

Videotron Ltee

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
287
1.8% of its addresses · 30 days
Always-on exits
34
12% of its exits
Spread
60 of 64
/24s with at least one exit
Providers
122
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

168K observations
  • VPN · anonymizer
  • Residential

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HydraProxy
  • INSTANTSOCKS_BASIC
  • IP2WORLD
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LOKIPROXY
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PSBProxy
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
record created Oct 12, 2012
2 · Leased from
not leased
3 · Announced by
AS5769 Videotron Ltee
since Nov 2012 · 14.0 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 166.62.128.0/18/24s
VPN GateUniversity of Tsukuba
20.01%
2

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

166.62.128.0/18

From the registry to its use

  1. Oct 12, 2012
    Registry record
    Videotron Ltee
    Direct Allocation
    166.62.128.0/17
  2. Oct 16, 2012
    Route object
    AS5769 Videotron Ltee
    RADB route object for AS5769 Videotron Ltee, maintainer MAINT-AS5769
  3. Nov 1, 2012– today
    Announced
    AS5769 Videotron Ltee
    as part of 166.62.128.0/17
    166.62.128.0/17
  4. Nov 1, 2012– today
    Announced
    AS5769 Videotron Ltee
    Internet provider
  5. Jul 2, 2025
    Route object
    AS5769 Videotron Ltee
    ARIN route object for AS5769 Videotron Ltee, maintainer MNT-VL-421
  6. today
    Used
    VPN Gate
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
166.62.128.0/17
since Nov 2012
AS5769Residential615
105 always on
Videotron Ltee

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
166.62.128.0/1732,768VL-28BLVideotron Ltee (VL-421) · CADirect AllocationOct 12, 2012abuse@videotron.ca
└ 166.62.128.0/24256VL-BKBN-BB-A63E8000unknown———
└ 166.62.129.0/24256VL-DHCPVIDEOTRON-MB-A63E8100unknown———
└ 166.62.130.0/24256VL-DHCPVIDEOTRON-MB-A63E8200unknown———
└ 166.62.131.0/24256VL-DHCPVIDEOTRON-FOVL-A63E8300unknown———
└ 166.62.132.0/24256VL-DHCPVIDEOTRON-STFE-A63E8400unknown———
└ 166.62.133.0/24256VL-DHCPVIDEOTRON-CC-A63E8500unknown———
└ 166.62.134.0/24256VL-DHCPVIDEOTRON-MK-A63E8600unknown———
└ 166.62.135.0/24256VL-DHCPVIDEOTRON-MK-A63E8700unknown———
└ 166.62.136.0/24256VL-DHCPVIDEOTRON-CC-A63E8800unknown———
└ 166.62.137.0/24256VL-DHCPVIDEOTRON-CC-A63E8900unknown———
└ 166.62.138.0/24256VL-DHCPVIDEOTRON-CC-A63E8A00unknown———
└ 166.62.139.0/24256VL-DHCPVIDEOTRON-CC-A63E8B00unknown———
└ 166.62.140.0/24256VL-DHCPVIDEOTRON-CS-A63E8C00unknown———
└ 166.62.141.0/24256VL-DHCPVIDEOTRON-ERBL-A63E8D00unknown———
└ 166.62.142.0/24256VL-DHCPVIDEOTRON-MZ-A63E8E00unknown———
└ 166.62.143.0/24256VL-DHCPVIDEOTRON-CC-A63E8F00unknown———
└ 166.62.144.0/24256VL-DHCPVIDEOTRON-MW-A63E9000unknown———
└ 166.62.145.0/24256VL-DHCPVIDEOTRON-MW-A63E9100unknown———
└ 166.62.146.0/24256VL-DHCPVIDEOTRON-OH-A63E9200unknown———
└ 166.62.147.0/24256VL-DHCPVIDEOTRON-OH-A63E9300unknown———
└ 166.62.148.0/24256VL-DHCPVIDEOTRON-OH-A63E9400unknown———
└ 166.62.149.0/24256VL-DHCPVIDEOTRON-CC-A63E9500unknown———
└ 166.62.150.0/24256VL-DHCPVIDEOTRON-MK-A63E9600unknown———
└ 166.62.151.0/24256VL-DHCPVIDEOTRON-MK-A63E9700unknown———
└ 166.62.152.0/24256VL-DHCPVIDEOTRON-MK-A63E9800unknown———
└ 166.62.153.0/24256VL-DHCPVIDEOTRON-CC-A63E9900unknown———
└ 166.62.154.0/24256VL-DHCPVIDEOTRON-MZ-A63E9A00unknown———
└ 166.62.155.0/24256VL-DHCPVIDEOTRON-QG-A63E9B00unknown———
└ 166.62.156.0/24256VL-DHCPVIDEOTRON-MZ-A63E9C00unknown———
└ 166.62.157.0/24256VL-DHCPVIDEOTRON-OH-A63E9D00unknown———
└ 166.62.158.0/24256VL-DHCPVIDEOTRON-SBVL-A63E9E00unknown———
└ 166.62.159.0/24256VL-DHCPVIDEOTRON-DLNR-A63E9F00unknown———
└ 166.62.160.0/24256VL-DHCPVIDEOTRON-MZ-A63EA000unknown———
└ 166.62.161.0/24256VL-DHCPVIDEOTRON-AMBA-A63EA100unknown———
└ 166.62.162.0/24256VL-DHCPVIDEOTRON-QG-A63EA200unknown———
└ 166.62.163.0/24256VL-DHCPVIDEOTRON-MZ-A63EA300unknown———
└ 166.62.164.0/24256VL-DHCPVIDEOTRON-CC-A63EA400unknown———
└ 166.62.165.0/24256VL-DHCPVIDEOTRON-QG-A63EA500unknown———
└ 166.62.166.0/24256VL-DHCPVIDEOTRON-MZ-A63EA600unknown———
└ 166.62.167.0/24256VL-DHCPVIDEOTRON-ML-A63EA700unknown———
└ 166.62.168.0/24256VL-DHCPVIDEOTRON-ML-A63EA800unknown———
└ 166.62.169.0/24256VL-DHCPVIDEOTRON-CC-A63EA900unknown———
└ 166.62.170.0/24256VL-DHCPVIDEOTRON-CC-A63EAA00unknown———
└ 166.62.171.0/24256VL-DHCPVIDEOTRON-QG-A63EAB00unknown———
└ 166.62.172.0/24256VL-DHCPVIDEOTRON-MZ-A63EAC00unknown———
└ 166.62.173.0/24256VL-DHCPVIDEOTRON-QG-A63EAD00unknown———
└ 166.62.174.0/24256VL-DHCPVIDEOTRON-MZ-A63EAE00unknown———
└ 166.62.175.0/24256VL-DHCPVIDEOTRON-ME-A63EAF00unknown———
└ 166.62.176.0/24256VL-DHCPVIDEOTRON-M6-A63EB000unknown———
└ 166.62.177.0/24256VL-DHCPVIDEOTRON-ME-A63EB100unknown———
└ 166.62.178.0/24256VL-DHCPVIDEOTRON-ME-A63EB200unknown———
└ 166.62.179.0/24256VL-DHCPVIDEOTRON-MC-A63EB300unknown———
└ 166.62.180.0/24256VL-DHCPVIDEOTRON-MC-A63EB400unknown———
└ 166.62.181.0/24256VL-DHCPVIDEOTRON-ML-A63EB500unknown———
└ 166.62.182.0/24256VL-DHCPVIDEOTRON-MC-A63EB600unknown———
└ 166.62.183.0/24256VL-DHCPVIDEOTRON-MC-A63EB700unknown———
└ 166.62.184.0/24256VL-DHCPVIDEOTRON-MC-A63EB800unknown———
└ 166.62.185.0/24256VL-DHCPVIDEOTRON-M6-A63EB900unknown———
└ 166.62.186.0/24256VL-DHCPVIDEOTRON-MF-A63EBA00unknown———
└ 166.62.187.0/24256VL-DHCPVIDEOTRON-MK-A63EBB00unknown———
└ 166.62.188.0/24256VL-DHCPVIDEOTRON-MK-A63EBC00unknown———
└ 166.62.189.0/24256VL-DHCPVIDEOTRON-MK-A63EBD00Videotron Ltee (C03207160) · CAReassignedNov 14, 2012abuse@videotron.ca
via VL-28BL
└ 166.62.190.0/24256VL-DHCPVIDEOTRON-MZ-A63EBE00Videotron Ltee (C03207161) · CAReassignedNov 14, 2012abuse@videotron.ca
via VL-28BL
└ 166.62.191.0/24256VL-DHCPVIDEOTRON-M6-A63EBF00unknown———

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

16,384 addresses
TypeAddressesShareRanges
Residential16,382>99%3
VPNanonymizer20.01%2

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2012
Current origin since
Nov 2012 · 14 yr
Origin networks
1