Data as of Nov 20, 2026

213.40.92.0/24

7 residential-proxy exits · 30 days

Internexus Networks Limited

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
29
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • ByteProxies
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FROXY
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GloryCloud
  • HASDATA
  • IPMUSK
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • ProxyEmpire
  • Proxyma
  • Q2IP
  • Shifter
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.40.0.0/16
since Feb 2010
AS9142Residential606
46 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.50.8 - 213.40.127.25519,960NETLINE-UKInternexus (6G)ASSIGNED PADec 23, 2010imtiaz.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.88.0/21

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Mar 2022 · 4.7 yr
Origin networks
1