Data as of Nov 13, 2026

213.40.131.0/24

11 residential-proxy exits · 30 days

Internexus Networks Limited

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Providers
44
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

7.5K observations

Proxy providers listing exits

  • 2Extract
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYWING_BASIC
  • PYPROXY
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • Q2IP
  • QUANTICDATA
  • RainProxy
  • Shifter
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.40.0.0/16
since Feb 2010
AS9142Residential605
34 always on
Internexus Networks Limited

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.40.0.0/1665,536VG-INTERNEXUS1-19990716Internexus Networks Limited (ORG-INL27-RIPE) · VGALLOCATED PAMay 14, 2024imtiaz.ahmed@internexus.co.uk
└ 213.40.128.0/1732,768NETLINE-UKInternexus (6G)ASSIGNED PAFeb 25, 2005imtiaz.ahmed@internexus.co.uk
via VG-INTERNEXUS1-19990716

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

213.40.128.0/20

Routing history

Pattern
Stable
First seen
Jun 2023
Current origin since
Jun 2023 · 3.4 yr
Origin networks
1