Data as of Nov 22, 2026

216.71.38.0/23

11 residential-proxy exits · 30 days

Midcontinent Communications

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

Residential-proxy exits

Proxy exits
11
2.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

13K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
216.71.39.0/2417
216.71.38.0/2404

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BottingTools
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GloryCloud
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • Proxy302
  • ProxyEmpire
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
216.71.0.0/1816,384NET-216-71-0-0-18Midcontinent Communications (MIDCO-1) · USDirect AllocationDec 5, 2016abuse@midco.com
└ 216.71.38.0/23512NET-216-71-38-0-23-DHCPunknown———

Network & registry

Routing timeline

Who has announced 216.71.0.0/18

216.71.0.0/18

Routing history

Pattern
Stable
First seen
Aug 2010
Current origin since
Dec 2016 · 9.9 yr
Origin networks
2
Last change of origin
Dec 2016
Recorded history

History

Handoffs
1