Data as of Nov 18, 2026

31.173.176.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
26
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FlexyProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,281
64 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.176.0/204,096MF-GNOC-PF-AS35298-20150325Volga Branch of OJSC MegaFon - AS35298LIR-PARTITIONED PAMar 27, 2015abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.176.0/24256MF-PF-20220810unknownASSIGNED PAAug 11, 2022abuse-mailbox@megafon.ru
via MF-GNOC-PF-AS35298-20150325

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.176.0/20

Routing history

Pattern
Stable
First seen
Aug 2012
Current origin since
Apr 2015 · 12 yr
Origin networks
2
Last change of origin
Apr 2015
Recorded history

History

Handoffs
1