Data as of Nov 20, 2026

70.188.182.0/24

5 residential-proxy exits · 30 days

Cox Communications Inc.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
28
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • BirdProxies
  • Bright Data
  • Byteful
  • ColaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPROCKET_BASIC
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
70.160.0.0/11AS22773Residential27,470
6,156 always on
Cox Communications Inc.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
70.160.0.0/112,097,152NETBLK-COX-ATLANTA-10Cox Communications Inc. (CXA) · USDirect AllocationJul 21, 2004abuse@charter.net
└ 70.188.128.0/1816,384NETBLK-RI-RDC-70-188-128-0Cox Communications (C01012170) · USReassignedFeb 8, 2005abuse@charter.net
via NETBLK-COX-ATLANTA-10

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

70.188.128.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1