Data as of Nov 18, 2026

178.177.22.0/24

14 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Providers
27
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

149 observations

Proxy providers listing exits

  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPROCKET_BASIC
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,824
288 always on
PJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each 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.177.0.0/1816,384MF-STF-20200910-T3273687Metropolitan branch of PJSC MegaFon, MoscowLIR-PARTITIONED PASep 10, 2020abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.177.0.0/198,192MF-STF-21062023unknownSUB-ALLOCATED PAJun 21, 2023abuse-mailbox@megafon.ru
via MF-STF-20200910-T3273687

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

178.177.0.0/18

Routing history

Pattern
Stable
First seen
Sep 2020
Current origin since
Sep 2020 · 6.2 yr
Origin networks
1