Data as of Nov 17, 2026

31.173.26.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
4
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • NovProxy
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,283
60 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.0.0/198,192MF-GDC-28062022unknownLIR-PARTITIONED PAJun 28, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.24.0/212,048MF-MOSCOW-MBB-FIXEDIP-31-173-24-0GPRS pool for APN fixedIP.mskASSIGNED PAAug 28, 2020abuse-mailbox@megafon.ru
via MF-GDC-28062022

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

Routing history

Pattern
Stable
First seen
Nov 2016
Current origin since
Nov 2016 · 10 yr
Origin networks
1