Data as of Nov 16, 2026

109.74.112.0/20

2 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.05% of its addresses · 30 days
Spread
2 of 16
/24s with at least one exit
Providers
20
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

356 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
109.74.115.0/2401
109.74.120.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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.74.112.0/204,096RU-MEGAFON-20091029PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAOct 29, 2009abuse-mailbox@megafon.ru
└ 109.74.112.0/212,048SZKTI-NETJSC SzktiASSIGNED PAOct 30, 2009abuse-mailbox@megafon.ru
via RU-MEGAFON-20091029
└ 109.74.120.0/212,048SZKTI-NETJSC SzktiASSIGNED PAApr 21, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-20091029

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
Rotating
First seen
Nov 2009
Current origin since
Aug 2023 · 3.3 yr
Origin networks
2
Last change of origin
Aug 2023
Recorded history

History

Handoffs
1