Data as of Nov 21, 2026

207.204.102.0/24

11 residential-proxy exits · 30 days

FLOW

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Providers
45
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • GEEKPROXY_TURBO
  • Geonode
  • GonzoProxy
  • IP2WORLD
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NSocks
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Thordata
  • TrueProxies
  • VantageProxies
  • Webshare
  • ZENPROXY_LITE

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
207.204.64.0/1816,384CCJL-NET-BLK03FLOW (CCJL) · JMDirect AllocationMay 6, 2009cwc-csirt@cwc.com
└ 207.204.102.0/24256CCJL-H8-CMTS-C4-207-204-102-0unknownReassignedJun 14, 2011cwc-csirt@cwc.com
via CCJL-NET-BLK03

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 207.204.96.0/21

207.204.96.0/21

Routing history

Pattern
Stable
First seen
Nov 2009
Current origin since
Nov 2009 · 17 yr
Origin networks
2
Last change of origin
Mar 2020
Recorded history

History

Handoffs
1