Data as of Nov 17, 2026

206.83.24.0/23

7 residential-proxy exits · 30 days

Wabash Independent Networks

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

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Always-on exits
2
29% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
39
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
206.83.24.0/2426
206.83.25.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • Bright Data
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
206.83.16.0/204,096WABASHINDEPENDENTNETWORKSWabash Independent Networks (WIN-8) · USDirect AllocationNov 30, 2004winita@wabash.net
└ 206.83.24.0/23512NET-206-83-24-0Wabash Telephone Coop, Inc (C03401815) · USReassignedMay 16, 2013winita@wabash.net
via WABASHINDEPENDENTNETWORKS

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 206.83.16.0/20

206.83.16.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Sep 2012 · 14 yr
Origin networks
2
Last change of origin
Sep 2012
Recorded history

History

Handoffs
1