Data as of Nov 16, 2026

31.173.187.0/24

1 residential-proxy exit · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3 observations

Proxy providers listing exits

  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.176.0/20
since Apr 2015
AS35298Mobile38
9 always on
PJSC MegaFon
via Volga Branch of OJSC MegaFon - AS35298
31.173.0.0/16
since Feb 2020
AS31133Mobile4,291
60 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.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.187.0/24256MF-PF-20220811unknownASSIGNED 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

Summary

Routing history

Pattern
Stable
First seen
Nov 2012
Current origin since
Mar 2019 · 7.7 yr
Origin networks
2
Last change of origin
Mar 2019
Recorded history

History

Handoffs
1