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

212.30.41.0/24

93 residential-proxy exits · 30 days

farahnet · space held by M Nets SAL

Announcement
this exact prefix
RPKI valid
Announced by
AS43019
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
93
36% of its addresses · 30 days
Always-on exits
90
97% of its exits
Providers
45
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

146K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FlashProxy
  • Geonode
  • GloryCloud
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • Kookey
  • Maskify
  • Novada
  • Oxylabs
  • PacketStream
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalData
  • VitalExclusive

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
212.30.32.0/198,192LB-MNET-20080916M Nets SAL (ORG-MNS14-RIPE) · LBALLOCATED PASep 16, 2008admin@mnets.net
└ 212.30.41.0/24256user-poolunknownASSIGNED PAAug 5, 2024admin@mnets.net
via LB-MNET-20080916

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 historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Jun 2009
Current origin since
Jul 2024 · 2.3 yr
Origin networks
5
Last change of origin
Jul 2024
Recorded history

History

Handoffs
4