Data as of Nov 12, 2026

178.176.240.0/22

3 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
3
0.29% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
27
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

601 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • GSocks
  • Infatica
  • LemonPrime
  • MagneticProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYWING_BASIC
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • 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.240.0/212,048MF-GDC-09112022unknownLIR-PARTITIONED PANov 9, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.176.240.0/221,024APN-public-sibunknownASSIGNED PAJan 25, 2023abuse-mailbox@megafon.ru
via MF-GDC-09112022

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