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

5.172.0.0/19

1 anonymizer address · 0.01% · VPN253 residential-proxy exits · 30 days

Insys LLC

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

Residential-proxy exits

Proxy exits
253
3.1% of its addresses · 30 days
Always-on exits
27
11% of its exits
Spread
27 of 32
/24s with at least one exit
Providers
100
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

50K observations
  • VPN · anonymizer
  • Residential

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.172.9.0/24416
5.172.0.0/24317
5.172.7.0/2434
5.172.13.0/24213
5.172.5.0/24210
5.172.2.0/2427
5.172.27.0/2425
5.172.16.0/24121
5.172.8.0/24111
5.172.14.0/24111
5.172.4.0/24110
5.172.22.0/24110
5.172.26.0/2416
5.172.24.0/2416
5.172.30.0/2415
5.172.28.0/2414
5.172.12.0/24014
5.172.25.0/24013
5.172.6.0/24012
5.172.10.0/2409
5.172.15.0/2408
5.172.11.0/2408
5.172.3.0/2408
5.172.29.0/2408

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PSBProxy
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
Insys LLC
record created Jul 30, 2012
2 · Leased from
not leased
3 · Announced by
AS28890 Insys LLC
since Sep 2012 · 14.2 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 5.172.0.0/19/24s
VPN GateUniversity of Tsukuba
10.01%
1

Lineage

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

5.172.0.0/19

From the registry to its use

  1. Jul 30, 2012
    Registry record
    Insys LLC
    ALLOCATED PA
    5.172.0.0/19
  2. Aug 2, 2012
    Route object
    AS28890 Insys LLC
    RIPE route object for AS28890 Insys LLC, maintainer INSYS-MNT
  3. Sep 1, 2012– today
    Announced
    AS28890 Insys LLC
    Internet provider
  4. Jun 30, 2023
    Route object
    AS28890 Insys LLC
    RIPE route object for AS28890 Insys LLC, maintainer INSYS-MNT
    5.172.28.0/24
  5. Aug 12, 2024
    Route object
    AS28890 Insys LLC
    RIPE route object for AS28890 Insys LLC, maintainer INSYS-MNT
    5.172.19.0/24
  6. today
    Used
    VPN Gate
    VPN

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
5.172.0.0/198,192RU-INSYS-20120730Insys LLC (ORG-IJ1-RIPE) · RUALLOCATED PAJul 30, 2012abuse@profintel.ru
└ 5.172.0.0/212,048INSYS-SV-21Ekaterinburg CustomersASSIGNED PAAug 8, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.8.0/23512INSYS-SV-22Ekaterinburg CustomersASSIGNED PAAug 27, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.10.0/23512INSYS-SV-23Ekaterinburg CustomersASSIGNED PAAug 27, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.12.0/221,024INSYS-SV-24Ekaterinburg CustomersASSIGNED PAAug 27, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.16.0/221,024INSYS-EKB-8Ekaterinburg CustomersASSIGNED PASep 21, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.20.0/221,024INSYS-SV-25Ekaterinburg CustomersASSIGNED PASep 21, 2012abuse@profintel.ru
via RU-INSYS-20120730
└ 5.172.24.0/212,048INSYS-SV-26Home CustomersASSIGNED PAAug 27, 2012abuse@profintel.ru
via RU-INSYS-20120730

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

8,192 addresses
TypeAddressesShareRanges
Residential8,191>99%2
VPNanonymizer10.01%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

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