Data as of Nov 16, 2026

65.245.176.0/24

7 residential-proxy exits · 30 days

Co-Mo Comm Inc · space held by Verizon Business

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
44
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.245.176.0/20
since Feb 2020
AS33616Residential34
5 always on
Verizon Business
65.240.0.0/13
since May 2005
AS701Internet provider135
7 always on
Verizon Business

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
65.240.0.0 - 65.253.255.255917,504UUNET65-2Verizon Business (MCICS) · USDirect AllocationFeb 13, 2002abuse@verizon.com
└ 65.245.176.0/204,096CO-MO-CONNECTCo-Mo Comm Inc (CC-441) · USReassignedNov 29, 2016—

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jun 2019
Current origin since
Jun 2019 · 7.4 yr
Origin networks
1