Data as of Nov 10, 2026

69.174.166.0/24

2 residential-proxy exits · 30 days

Metronet

Announcement
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
6
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

36 observations

Proxy providers listing exits

  • FastProxy
  • IPFly
  • LemonBright
  • LudaxProxy
  • PuraRoute
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
69.174.160.0/20
since Sep 2013
AS30600Residential84
20 always on
Metronet

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, 2009TierIII@metronetinc.com
└ 69.174.166.0/2664CINER-3-69-174-166-0-26Static pool - Cinergy MetroNet (C07547514) · USReassignedMay 5, 2020TierIII@metronetinc.com
via NETBLK-CMN-IPV4-CIDR-01
└ 69.174.166.64/2664CINER-3-69-174-166-64-26Metronet - Static Pool#1 (C07558939) · USReassignedMay 29, 2020TierIII@metronetinc.com
via NETBLK-CMN-IPV4-CIDR-01
└ 69.174.166.128/25128CINER-3-69-174-166-128-25MetroNet - Carrier Grade NAT Pool (C07561560) · USReassignedJun 4, 2020TierIII@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

Covering aggregate above, the prefix's own history below

69.174.166.0/23

Routing history

Pattern
Stable
First seen
Mar 2022
Current origin since
Mar 2022 · 4.7 yr
Origin networks
1