Data as of Nov 12, 2026

31.173.76.0/22

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.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

108 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
31.173.77.0/2401
31.173.79.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • CatProxies
  • FloppyData
  • Geonode
  • HideProxy
  • IPFly
  • Novada
  • ProxiesVision
  • ProxyGeo
  • ProxyWing
  • PuraRoute
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,303
57 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.72.0/212,048MF-MOSCOW-BBA-POOL-31-173-72Megafon-Moscow Broadband clients poolLIR-PARTITIONED PAJul 6, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.76.0/221,024MF-STF-21062023unknownSUB-ALLOCATED PAJun 21, 2023abuse-mailbox@megafon.ru
via MF-MOSCOW-BBA-POOL-31-173-72

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.72.0/21

Routing history

Pattern
Stable
First seen
Apr 2015
Current origin since
Apr 2015 · 12 yr
Origin networks
1