Data as of Nov 18, 2026

109.75.240.0/20

62 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
62
1.5% of its addresses · 30 days
Always-on exits
5
8.1% of its exits
Spread
6 of 16
/24s with at least one exit
Providers
65
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

25K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
109.75.242.0/23
since Jul 2017
AS12714Mobile7PJSC MegaFon
109.75.249.0/24
since Jul 2017
AS12714Mobile10
1 always on
PJSC MegaFon
109.75.252.0/24
since Feb 2023
AS12714Mobile9
2 always on
PJSC MegaFon
109.75.253.0/24
since Feb 2023
AS12714Mobile15
1 always on
PJSC MegaFon
109.75.254.0/24
since Feb 2023
AS12714Mobile12
1 always on
PJSC MegaFon
109.75.255.0/24
since Feb 2023
AS12714Mobile9PJSC MegaFon

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.75.240.0/204,096RU-MEGAFON-20091125PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PANov 25, 2009abuse-mailbox@megafon.ru
└ 109.75.240.0/212,048TI-BBcustomers broadband aggregationASSIGNED PASep 11, 2013abuse-mailbox@megafon.ru
via RU-MEGAFON-20091125
└ 109.75.248.0/24256RU-TI-CUSTOMER-NETSUE OO "Road Service"ASSIGNED PAOct 10, 2013abuse-mailbox@megafon.ru
via RU-MEGAFON-20091125
└ 109.75.252.0/221,024PGTS-NETOJSC "Pskovskaya Gorodskaya Telefonnaya Set"ASSIGNED PASep 20, 2017abuse-mailbox@megafon.ru
via RU-MEGAFON-20091125

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
Oct 2015
Current origin since
Oct 2015 · 11 yr
Origin networks
1