LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

213.40.158.0/24

5 residential-proxy exits · 30 days

Internexus Networks Limited

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

285 observations

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BlurPath
  • Byteful
  • CliProxy
  • FastProxy
  • GSocks
  • Geonode
  • GoProxies
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxy4U
  • ProxyGeo
  • RainProxy
  • Shifter
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.40.0.0/16
since Feb 2010
AS9142Residential616
50 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

AnnouncementRouting historyWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

213.40.144.0/20

Routing history

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