Data as of Nov 13, 2026

178.176.61.0/24

6 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

891 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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.56.0/212,048MF-CENTER-178-176-56-2018-05-10Center Branch of OJSC MegaFon, FBB12LIR-PARTITIONED PAMay 10, 2018abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.176.61.0/24256MF-CF-07072022unknownASSIGNED PAJul 7, 2022abuse-mailbox@megafon.ru
via MF-CENTER-178-176-56-2018-05-10

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
May 2018
Current origin since
Mar 2019 · 7.7 yr
Origin networks
1