LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

184.83.0.0/16

722 residential-proxy exits · 30 days

Midcontinent Communications

Announcement
this exact prefix
RPKI valid
Announced by
AS11232
Type
Residential

Residential-proxy exits

Proxy exits
722
1.1% of its addresses · 30 days
Always-on exits
71
9.8% of its exits
Spread
212 of 256
/24s with at least one exit
Providers
118
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

361K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
184.83.237.0/2435
184.83.95.0/24210
184.83.28.0/2429
184.83.50.0/2428
184.83.158.0/2426
184.83.84.0/2425
184.83.60.0/2424
184.83.226.0/2424
184.83.228.0/2424
184.83.73.0/2423
184.83.122.0/2423
184.83.7.0/2419
184.83.66.0/2419
184.83.189.0/2417
184.83.148.0/2416
184.83.34.0/2416
184.83.229.0/2416
184.83.167.0/2416
184.83.76.0/2415
184.83.38.0/2415
184.83.211.0/2415
184.83.192.0/2415
184.83.61.0/2415
184.83.96.0/2415

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • MrScraper
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • WealthProxies
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
184.83.66.0/23
since Apr 2023
AS11232Residential13
1 always on
Midcontinent Communications

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
184.83.0.0/1665,536NET-184-83-0-0-16Midcontinent Communications (MIDCO-1) · USDirect AllocationSep 11, 2017abuse@midco.com
└ 184.83.14.0/23512NET-184-83-14-0-23-DHCPunknown———
└ 184.83.16.0/23512NET-184-83-16-0-23-DHCPunknown———
└ 184.83.18.0/23512NET-184-83-18-0-23-DHCPunknown———
└ 184.83.54.0/23512NET-184-83-54-0-23-DHCPunknown———
└ 184.83.56.0/23512NET-184-83-56-0-23-DHCPunknown———
└ 184.83.58.0/23512NET-184-83-58-0-23-DHCPunknown———
└ 184.83.64.0/23512NET-184-107-36-0-23-DHCPunknown———
└ 184.83.66.0/23512NET-184-83-66-0-23-DHCPMidcontinent Communications (C10855762) · USReassignedMay 28, 2024abuse@midco.com
via NET-184-83-0-0-16
└ 184.83.120.0/23512NET-184-83-120-0-23-DHCPunknown———
└ 184.83.122.0/23512NET-184-83-122-0-23-DHCPunknown———
└ 184.83.124.0/23512NET-184-83-124-0-23-DHCPunknown———
└ 184.83.126.0/23512NET-184-83-126-0-23-DHCPunknown———
└ 184.83.134.0/23512NET-183-83-134-0-23-DHCPunknown———
└ 184.83.158.0/23512NET-184-83-158-0-23-DHCPunknown———
└ 184.83.160.0/23512NET-184-83-160-0-23-DHCPunknown———
└ 184.83.164.0/23512NET-184-83-164-0-23-DHCPunknown———
└ 184.83.166.0/23512NET-184-83-166-0-23-DHCPunknown———
└ 184.83.188.0/23512NET-184-83-188-0-23-DHCPunknown———
└ 184.83.212.0/23512NET-184-83-212-0-23-DHCPunknown———
└ 184.83.218.0/23512NET-184-83-218-0-23-DHCPunknown———
└ 184.83.220.0/23512NET-184-83-220-0-23-DHCPunknown———
└ 184.83.224.0/23512NET-184-83-224-0-23-DHCPunknown———
└ 184.83.228.0/23512NET-184-83-228-0-23-DHCPunknown———
└ 184.83.250.0/23512NET-184-83-250-0-23-DHCPunknown———
└ 184.83.252.0/23512NET-184-83-252-0-23-DHCPunknown———

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

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