Data as of Nov 21, 2026

31.173.134.0/24

4 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
33
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

857 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GSocks
  • GonzoProxy
  • IPMUSK
  • IPOasis
  • IPPeak
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

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

Registrations in this block

The registry's network records over this block, widest first, each 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

31.173.134.0/23

Routing history

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