Data as of Nov 16, 2026

213.40.0.0/24

3 residential-proxy exits · 30 days

Internexus Networks Limited

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
28
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

211 observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • Byteful
  • Evomi
  • FastProxy
  • GSocks
  • GhostConnect
  • GloryCloud
  • IPFly
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.40.0.0/16
since Feb 2010
AS9142Residential594
33 always on
Internexus Networks Limited

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
213.40.0.0/1665,536VG-INTERNEXUS1-19990716Internexus Networks Limited (ORG-INL27-RIPE) · VGALLOCATED PAMay 14, 2024imtiaz.ahmed@internexus.co.uk
└ 213.40.0.0 - 213.40.49.25512,800NETLINE-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

Summary

Routing history

Pattern
Stable
First seen
Jul 2021
Current origin since
Jun 2023 · 3.5 yr
Origin networks
1