Data as of Nov 17, 2026

70.40.245.0/24

11 residential-proxy exits · 30 days

NetNet

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Providers
37
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BottingTools
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • HELODATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
70.40.224.0/19
since Nov 2008
AS3663Mobile166
1 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

Routing timeline

Covering aggregate above, the prefix's own history below

70.40.240.0/20

Routing history

Pattern
Stable
First seen
Jan 2023
Current origin since
Jan 2023 · 3.8 yr
Origin networks
1