Data as of Nov 21, 2026

31.173.134.0/23

9 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
9
1.8% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
43
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

10K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
31.173.135.0/2415
31.173.134.0/2404

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • IPMUSK
  • IPOasis
  • IPPeak
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,276
72 always on
PJSC MegaFon
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
31.173.135.0/24
since Apr 2020
AS31195Mobile5
1 always on
PJSC 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
31.173.0.0/1665,536RU-MEGAFON-20110404PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAOct 16, 2014abuse-mailbox@megafon.ru
└ 31.173.132.0/221,024MF-DVunknownLIR-PARTITIONED PASep 16, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.134.0/23512MF-DVF-FIXunknownASSIGNED PAJul 20, 2022abuse-mailbox@megafon.ru
via MF-DV

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2016
Current origin since
Dec 2016 · 10.0 yr
Origin networks
1