Data as of Nov 16, 2026

66.252.56.0/22

5 residential-proxy exits · 30 days

GoNetSpeed

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
66.252.59.0/2412
66.252.56.0/2403

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FloppyData
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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.252.32.0/198,192MMCOMM-BLK-2GoNetSpeed (OTELC) · USDirect AllocationApr 5, 2002otelco_abuse@gonetspeed.com
└ 66.252.56.0/221,024MMC-KNDS-DYNDSL-7MID-Maine Communications (C02028635) · USReassignedSep 5, 2008otelco_abuse@gonetspeed.com
via MMCOMM-BLK-2

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 2013
Current origin since
Mar 2017 · 9.7 yr
Origin networks
1