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

5.32.139.0/24

5 residential-proxy exits · 30 days

MEGA M, d.o.o.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
30
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

165 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Geonode
  • GloryCloud
  • IPFly
  • IPRoyal
  • KindProxy
  • LemonBright
  • MoMoProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • RainProxy
  • RapidProxy
  • RoamProxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • Webshare

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.32.136.0/212,048SI-MEGA-M-20120509MEGA M, d.o.o. (ORG-MMDV1-RIPE) · SIALLOCATED PAMay 9, 2012abuse@mega-m.net
└ 5.32.139.0/24256MEGA-M-DSLMega M, d.o.o., VelenjeASSIGNED PAApr 5, 2017abuse@mega-m.net
via SI-MEGA-M-20120509

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 5.32.136.0/21

5.32.136.0/21

Routing history

Pattern
Rotating
First seen
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
2
Last change of origin
Apr 2026
Recorded history

History

Handoffs
1