Data as of Nov 13, 2026

178.176.32.0/21

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

Exits seen per day

1.0K observations

/24s with the most always-on exits

Proxy providers listing exits

  • BottingTools
  • EnigmaProxy
  • IPFly
  • NovaProxy
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,819
269 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
178.176.0.0/14262,144RU-MEGAFON-20100122PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAJan 22, 2010abuse-mailbox@megafon.ru
└ 178.176.32.0/212,048MF-GNOC-STF-20180202PJSC MegaFon (ORG-OM1-RIPE) · RULIR-PARTITIONED PAMay 23, 2018abuse-mailbox@megafon.ru
└ 178.176.32.0/221,024MF-MOSCOW-BBA-POOL-178-176-32-0unknownASSIGNED PASep 9, 2020abuse-mailbox@megafon.ru
via MF-GNOC-STF-20180202
└ 178.176.36.0/221,024MF-MOSCOW-BBA-POOL-178-176-36-0unknownASSIGNED PASep 9, 2020abuse-mailbox@megafon.ru
via MF-GNOC-STF-20180202

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
Jun 2018
Current origin since
Jun 2018 · 8.4 yr
Origin networks
1