Data as of Nov 16, 2026

109.236.64.0/20

21 residential-proxy exits · 30 days

Non-public corporation MASARMAT

Announcement
this exact prefix
No RPKI
Announced by
Type
Unknown

Residential-proxy exits

Proxy exits
21
0.51% of its addresses · 30 days
Spread
9 of 16
/24s with at least one exit
Providers
51
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 911Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • PROXY_CC
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
109.236.64.0/22
since Dec 2009
AS39604Unknown1Non-public corporation MASARMAT
109.236.68.0/22
since Apr 2010
AS39604Unknown9Non-public corporation MASARMAT

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
109.236.64.0/204,096RU-MASARMAT-20091202Non-public corporation MASARMAT (ORG-JCM1-RIPE) · RUALLOCATED PADec 2, 2009abuse@masarmat.ru
└ 109.236.64.0/212,048NOVODANILOVSKIY-NETJSC "MASARMAT", MoscowASSIGNED PAMay 31, 2010abuse@masarmat.ru
via RU-MASARMAT-20091202
└ 109.236.72.0/212,048NOVODANILOVSKIY-NETunknownASSIGNED PAAug 13, 2012abuse@masarmat.ru
via RU-MASARMAT-20091202

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2010
Current origin since
Apr 2010 · 17 yr
Origin networks
1