Data as of Nov 17, 2026

206.83.19.0/24

4 residential-proxy exits · 30 days

Wabash Independent Networks

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
38
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

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.19.0/24256NET-206-83-19-0Wabash Telephone Coop, Inc (C03149475) · USReassignedSep 20, 2012winita@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