Data as of Nov 21, 2026

69.174.171.96/27

1 residential-proxy exit · 30 days

Metronet

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

Residential-proxy exits

Proxy exits
1
3.1% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
34
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

3.5K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • AnyIP
  • B2Proxy
  • BESTPROXY_NET
  • BUYPERSONALPROXY
  • CYBERYOZH
  • ColaProxy
  • EZProxies
  • FLAMEPROXIES_BASIC
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • GloryCloud
  • HASDATA
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LudaxProxy
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxy302
  • PuraRoute
  • RainProxy
  • SCRAPELESS
  • SPYDERPROXY_BASIC
  • Thordata
  • VitalExclusive
  • YumiProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
69.174.128.0 - 69.174.175.25512,288NETBLK-CMN-IPV4-CIDR-01Metronet (CINER-3) · USDirect AllocationApr 29, 2009abuse@metronetinc.com
└ 69.174.171.96/2732CINER-3-69-174-171-96-27Static - Cinergy MetroNet (C05993216) · USReassignedDec 21, 2015abuse@metronetinc.com
via NETBLK-CMN-IPV4-CIDR-01

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 69.174.160.0/20

69.174.160.0/20

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Sep 2013 · 13 yr
Origin networks
2
Last change of origin
Sep 2013
Recorded history

History

Handoffs
1