Data as of Nov 12, 2026

178.178.101.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
20
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

554 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BlurPath
  • Byteful
  • CliProxy
  • EnigmaProxy
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,854
268 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.178.96.0/198,192MF-FCURP-FIXunknownLIR-PARTITIONED PAAug 13, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.178.100.0/23512MF-FCURP_SzF_24_01_22SzF of PJSC MegaFon 178.178.100.0/23ASSIGNED PAJan 24, 2022abuse-mailbox@megafon.ru
via MF-FCURP-FIX

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.178.100.0/23

Routing history

Pattern
Stable
First seen
Aug 2022
Current origin since
Aug 2022 · 4.3 yr
Origin networks
1