Data as of Nov 10, 2026

178.178.136.0/24

1 residential-proxy exit · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

239 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,884
274 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.178.128.0/204,096MF-CF-20220705-T4116178unknownLIR-PARTITIONED PAJul 5, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.178.136.0/23512MF-CF-07072022unknownASSIGNED PAJul 7, 2022abuse-mailbox@megafon.ru
via MF-CF-20220705-T4116178

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
Nov 2022
Current origin since
Nov 2022 · 4.0 yr
Origin networks
1