Data as of Nov 13, 2026

37.28.176.0/22

3 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
3
0.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

232 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
37.28.176.0/2401
37.28.178.0/2401
37.28.179.0/2401

Proxy providers listing exits

  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • IPFly
  • LUMIPROXY
  • NSocks
  • NiuProxy
  • PROXY_CC
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.28.160.0/19
since Feb 2020
AS31133Mobile30
1 always on
PJSC 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.168.0 - 37.28.183.2554,096MF-GDC-18072023unknownLIR-PARTITIONED PAJul 18, 2023abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.28.176.0/221,024MF-MOSCOWMegaFon-Moscow GPRS Pool for APN fixedIP.mskASSIGNED PASep 7, 2012abuse-mailbox@megafon.ru
via MF-GDC-18072023

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

Routing history

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