Data as of Nov 20, 2026

191.223.220.0/24

8 residential-proxy exits · 30 days

DMIT Cloud Services · reallocated from NetCrew

Announcement
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
8
3.1% of its addresses · 30 days
Providers
32
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

210 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • Evomi
  • FLAMEPROXIES_BASIC
  • FlexyProxies
  • GSocks
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • Infatica
  • InfiniteProxies
  • KindProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • RainProxy
  • ResiProxies
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each 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 191.223.220.0/23

191.223.220.0/23

Routing history

Pattern
Stable
First seen
Jun 2026
Current origin since
Jun 2026 · 5 mo
Origin networks
1