Data as of Nov 11, 2026

178.176.136.0/24

5 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address · Proxy exits nearby

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
3
60% of its exits
Providers
37
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

18K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,891
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.128.0 - 178.176.138.2552,816MC-FCURPunknownLIR-PARTITIONED PAJul 29, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.176.136.0/23512MF-MC-18072022unknownASSIGNED PAJul 18, 2022abuse-mailbox@megafon.ru
via MC-FCURP

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
Sep 2019
Current origin since
Sep 2019 · 7.1 yr
Origin networks
1