Data as of Nov 20, 2026

191.223.220.0/23

14 residential-proxy exits · 30 days

DMIT Cloud Services · reallocated from NetCrew

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recent change
New origin Jun 2026
its first announcement on record
registry: reallocated to DMIT Cloud Services by NetCrew, Jun 22, 2026

Residential-proxy exits

Proxy exits
14
2.7% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
45
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

335 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
191.223.220.0/2408
191.223.221.0/2406

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPCola
  • IPOasis
  • Infatica
  • InfiniteProxies
  • KindProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PacketStream
  • PrivateByte
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • ResiProxies
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
191.223.208.0/204,096OL-406-4NetCrew (OL-406) · USDirect AllocationJun 22, 2026netabuse@opennetwork.ltd
└ 191.223.208.0/204,096OL-DMIT-4DMIT Cloud Services (DMITI) · USReallocatedJun 22, 2026abuse@dmit.com
└ 191.223.220.0/23512DMIT-CUSTOMER-TOKYO-1400002unknownReassignedJun 24, 2026abuse@dmit.com
via OL-406-4

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
Jun 2026
Current origin since
Jun 2026 · 5 mo
Origin networks
1