Data as of Nov 11, 2026

178.176.4.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
Always-on exits
1
50% of its exits
Providers
4
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

91 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • LemonPrime
  • PuraRoute

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 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.176.0.0/198,192MF-GNOC-STF-20180202PJSC MegaFon (ORG-OM1-RIPE) · RULIR-PARTITIONED PAFeb 2, 2018abuse-mailbox@megafon.ru
└ 178.176.0.0/204,096MF-MOSCOW-BBA-POOL-178-176-0-0unknownASSIGNED PASep 7, 2020abuse-mailbox@megafon.ru
via MF-GNOC-STF-20180202

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.176.0.0/19

Routing history

Pattern
Stable
First seen
Aug 2018
Current origin since
Aug 2018 · 8.2 yr
Origin networks
1