Data as of Nov 12, 2026

176.193.78.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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.193.72.0/21
since Feb 2023
AS12714Mobile34
3 always on
PJSC MegaFon
176.192.0.0/15
since Aug 2011
AS12714Mobile10,178
258 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
176.192.0.0/14262,144RU-MEGAFON-20110707PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAJul 7, 2011abuse-mailbox@megafon.ru
└ 176.192.0.0/15131,072NBN-NETNet By Net Holding LLCASSIGNED PAApr 28, 2014abuse-mailbox@megafon.ru
via RU-MEGAFON-20110707

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
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1