Data as of Nov 13, 2026

174.131.112.0/20

8 residential-proxy exits · 30 days

Windstream Communications LLC

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

Residential-proxy exits

Proxy exits
8
0.20% of its addresses · 30 days
Always-on exits
4
50% of its exits
Spread
7 of 16
/24s with at least one exit
Providers
60
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

12K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
174.130.0.0/15
since Jul 2008
AS7029Residential940
168 always on
Windstream Communications LLC

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
174.130.0.0/15131,072WINDSTREAMWindstream Communications LLC (WINDS-6) · USDirect AllocationJun 13, 2008abuse@windstream.net
└ 174.131.112.0/204,096174-131-112-0Windstream Communications LLC (C11005848) · USReassignedNov 4, 2024abuse@windstream.net
via WINDSTREAM

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Feb 2025 · 1.7 yr
Origin networks
1