Data as of Nov 17, 2026

162.253.108.0/22

2 residential-proxy exits · 30 days

Midcontinent Communications

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

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
22
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
162.253.111.0/2411
162.253.109.0/2401

Proxy providers listing exits

  • B2Proxy
  • BlurPath
  • CliProxy
  • FastProxy
  • GloryCloud
  • IPPeak
  • IPROCKET_BASIC
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PYPROXY
  • Proxiware
  • ProxyRack
  • Q2IP
  • RainProxy
  • ThunderProxy
  • TrueProxies
  • VitalExclusive
  • ZENPROXY_LITE

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
162.253.108.0/221,024INVISIMAX-108-111Midcontinent Communications (MIDCO-1) · USDirect AllocationFeb 13, 2014abuse@midco.com
└ 162.253.108.0/221,024NET-162-253-108-0-22Invisimax (C06981786) · USReassignedMay 14, 2018abuse@midco.com
via INVISIMAX-108-111

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Jan 2022 · 4.8 yr
Origin networks
2
Last change of origin
Sep 2017
Recorded history

History

Handoffs
1