Data as of Nov 18, 2026

178.177.40.0/24

No anonymizer space · no proxy exits in 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.177.0.0/18
since Sep 2020
AS25159Mobile62
5 always on
PJSC MegaFon
via Metropolitan branch of PJSC MegaFon, Moscow
178.176.0.0/14
since Feb 2020
AS31133Mobile30,874
285 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.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.32.0/198,192MF-STF-21062023unknownSUB-ALLOCATED PAJun 21, 2023abuse-mailbox@megafon.ru
via MF-STF-20200910-T3273687
└ 178.177.40.0/24256MF-STF-Cloud-DC2T4397920ASSIGNED PAMar 16, 2023abuse-mailbox@megafon.ru
via MF-STF-21062023

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
Mar 2023
Current origin since
Mar 2023 · 3.7 yr
Origin networks
1