Data as of Nov 22, 2026

191.222.223.0/24

3 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
3
1.2% of its addresses · 30 days
Providers
27
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

82 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • IPCola
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

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

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