Data as of Nov 20, 2026

66.60.248.0/21

25 residential-proxy exits · 30 days

Phonoscope, Inc.

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
25
1.2% of its addresses · 30 days
Always-on exits
5
20% of its exits
Spread
4 of 8
/24s with at least one exit
Providers
51
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

36K observations

/24s with the most always-on exits

Proxy providers listing exits

  • AETHYN_BASIC
  • Ake.net
  • AnyIP
  • BottingTools
  • Byteful
  • CliProxy
  • ColaProxy
  • Datarama
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • GloryCloud
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NSTPROXY_LITE
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYON
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
66.60.249.0/24
since Sep 2025
AS22442ResidentialPhonoscope, Inc.

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
66.60.246.0 - 66.60.255.2552,560PHONOSCOPE-NET-04Phonoscope, Inc. (PHONO-5) · USDirect AllocationMay 26, 2006abuse@phonoscope.com
└ 66.60.248.0/221,024PHONOSCOPE-66-60-248-0Phonoscope Cable Northwest Houston (C01913831) · USReassignedApr 1, 2008abuse@phonoscope.com
via PHONOSCOPE-NET-04
└ 66.60.252.0/221,024PHONOSCOPE-66-60-252-0unknown———

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