Data as of Nov 21, 2026

216.9.190.0/23

19 residential-proxy exits · 30 days

Orbitel Communications, LLC

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

Residential-proxy exits

Proxy exits
19
3.7% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
67
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

23K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
216.9.191.0/24011
216.9.190.0/2408

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • Ake.net
  • AnyIP
  • B2Proxy
  • BESTPROXY_NET
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • 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
216.9.176.0/204,096ORBITEL-RANCHOOrbitel Communications, LLC (OCL-29) · USDirect AllocationJul 12, 2007abuse@zcorum.com
└ 216.9.176.0/204,096ORBITEL-RANCHO-EL-DORADOOrbitel Communications, LLC (C01935011) · USReassignedMay 11, 2008abuse@zcorum.com
via ORBITEL-RANCHO

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
Dec 2020
Current origin since
Dec 2020 · 6.0 yr
Origin networks
1