LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

178.176.0.0/20

4 residential-proxy exits · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
4
0.10% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 16
/24s with at least one exit
Providers
7
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

108 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.176.4.0/2412
178.176.1.0/2401
178.176.7.0/2401

Proxy providers listing exits

  • BottingTools
  • IPFly
  • LemonPrime
  • NodeProxy
  • NovaProxy
  • PuraRoute
  • VantageProxies

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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