Data as of Nov 19, 2026

70.40.254.0/23

15 residential-proxy exits · 30 days

NetNet

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

Residential-proxy exits

Proxy exits
15
2.9% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

2.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
70.40.254.0/24010
70.40.255.0/2405

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BESTPROXY_NET
  • BUYPERSONALPROXY
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • HELODATA
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LITPORT_LIMA
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy302
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RoamProxy
  • SCRAPELESS
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
70.40.240.0/20
since Jan 2023
AS3663Mobile167
1 always on
NetNet
70.40.224.0/19
since Nov 2008
AS3663Mobile171
2 always on
NetNet

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
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

Summary

Routing history

Pattern
Stable
First seen
Dec 2022
Current origin since
Dec 2022 · 4.0 yr
Origin networks
1