Data as of Nov 20, 2026

191.223.208.0/24

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

Exits seen per day

301 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxy4U
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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.208.0/221,024DMIT-CUSTOMER-HKunknownReassignedJun 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.208.0/22

191.223.208.0/22

Routing history

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