Data as of Nov 14, 2026

178.176.134.0/23

11 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
11
2.1% of its addresses · 30 days
Always-on exits
8
73% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
45
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

20K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.176.134.0/2457
178.176.135.0/2434

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,797
273 always on
PJSC MegaFon
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
178.176.135.0/24
since Jan 2021
AS31133Mobile4
3 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.134.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 2020
Current origin since
Sep 2020 · 6.2 yr
Origin networks
1