Data as of Nov 19, 2026

37.28.190.0/23

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
17
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

92 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.28.160.0/19
since Feb 2020
AS31133Mobile29
1 always on
PJSC MegaFon
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
37.28.190.0/24
since Sep 2012
AS31195Mobile1PJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.28.160.0/198,192RU-MEGAFON-20111230PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PADec 30, 2011abuse-mailbox@megafon.ru
└ 37.28.190.0/23512MF-DVFunknownLIR-PARTITIONED PAJul 7, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.28.190.0/24256MF-DVBroadbandASSIGNED PAOct 11, 2012abuse-mailbox@megafon.ru
via MF-DVF
└ 37.28.191.0/24256MF-DVColocationASSIGNED PAOct 11, 2012abuse-mailbox@megafon.ru
via MF-DVF

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

37.28.188.0/22

Routing history

Pattern
Stable
First seen
Jul 2012
Current origin since
Jul 2012 · 14 yr
Origin networks
1