LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

70.40.239.0/24

4 residential-proxy exits · 30 days

NetNet

Announcement
70.40.224.0/20
RPKI valid
Announced by
AS3663
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.3K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • Byteful
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • GhostConnect
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
70.40.224.0/19
since Nov 2008
AS3663Mobile162
4 always on
NetNet

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
70.40.224.0/198,192NETNET-NETWORK-4NetNet (NETLE-1) · USDirect AllocationOct 3, 2008report_abuse@nsight.com
└ 70.40.224.0/198,192NETNET-70-40-224-0NetLEC/NetNet (C02598068) · USReassignedOct 1, 2010report_abuse@nsight.com
via NETNET-NETWORK-4

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

70.40.224.0/20

Routing history

Pattern
Stable
First seen
Apr 2024
Current origin since
Apr 2024 · 2.6 yr
Origin networks
1