Data as of Nov 17, 2026

193.30.9.0/24

8 residential-proxy exits · 30 days

Meswifi, SL

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

Residential-proxy exits

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

Exits seen per day

11K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 911Proxy
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GhostConnect
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
193.30.8.0/221,024ES-MESWIFISL-20180710Meswifi, SL (ORG-MS486-RIPE) · ESALLOCATED PASep 9, 2020ripe@meswifi.com
└ 193.30.9.0/24256ES-MESWIFISL-20181007unknownASSIGNED PAJul 10, 2018ripe@meswifi.com
via ES-MESWIFISL-20180710

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

Who has announced 193.30.8.0/22

193.30.8.0/22

Routing history

Pattern
Stable
First seen
Jun 2018
Current origin since
Jun 2018 · 8.4 yr
Origin networks
1