Data as of Nov 11, 2026

184.83.166.0/23

10 residential-proxy exits · 30 days

Midcontinent Communications

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

Residential-proxy exits

Proxy exits
10
2.0% of its addresses · 30 days
Always-on exits
2
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
55
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
184.83.167.0/2416
184.83.166.0/2414

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPRoyal
  • Infatica
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
184.83.0.0/1665,536NET-184-83-0-0-16Midcontinent Communications (MIDCO-1) · USDirect AllocationSep 11, 2017abuse@midco.com
└ 184.83.166.0/23512NET-184-83-166-0-23-DHCPunknown———

Network & registry

Routing timeline

Who has announced 184.83.0.0/16

184.83.0.0/16

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Oct 2017 · 9.1 yr
Origin networks
2
Last change of origin
Oct 2017
Recorded history

History

Handoffs
1