Data as of Nov 18, 2026

193.138.4.0/24

8 residential-proxy exits · 30 days

MVA S.r.l. · space held by Vela.net s.n.c.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
32
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPMUSK
  • IPRoyal
  • Infatica
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • NiuProxy
  • Oxylabs
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RapidProxy
  • SwiftProxy
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
193.138.4.0/23
since Oct 2019
AS202803Residential11
1 always on
Vela.net s.n.c.

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
193.138.4.0/23512IT-VELANET-20191011Vela.net s.n.c. (ORG-VS217-RIPE) · ITALLOCATED PASep 18, 2025abuse@velanet.info
└ 193.138.4.0/24256PRT-CLOUD-SERVERSunknownASSIGNED PANov 12, 2019abuse@velanet.info
via IT-VELANET-20191011

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
Oct 2019
Current origin since
Jun 2025 · 1.4 yr
Origin networks
1