Data as of Nov 13, 2026

31.173.136.0/24

2 residential-proxy exits · 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
2
0.78% of its addresses · 30 days
Providers
21
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

303 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.173.0.0/16
since Feb 2020
AS31133Mobile4,294
57 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.136.0 - 31.173.142.2551,792MF-VLGBNGLIR-PARTITIONED PASep 16, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20110404
└ 31.173.136.0/24256MF-PF-20220810BNGASSIGNED PADec 8, 2016abuse-mailbox@megafon.ru
via MF-VLG

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
Nov 2016 · 10.0 yr
Origin networks
2
Last change of origin
Nov 2016
Recorded history

History

Handoffs
1