Data as of Nov 20, 2026

31.173.209.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
3
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

38 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,274
72 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.202.0 - 31.173.223.2555,632MF-KF-20220507Fixed Broadband - Caucasus Branch of OJSC MegaFon AS31163LIR-PARTITIONED PAJul 5, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.209.0/24256MF-KAVKAZ-18082022-T4122797unknownASSIGNED PAOct 31, 2016abuse-mailbox@megafon.ru
via MF-KF-20220507

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
Apr 2015 · 12 yr
Origin networks
2
Last change of origin
Apr 2015
Recorded history

History

Handoffs
1