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

178.176.44.0/22

3 residential-proxy exits · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
13
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

49 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.176.47.0/2402
178.176.46.0/2401

Proxy providers listing exits

  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • Datarama
  • Evomi
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • NovaProxy
  • ProxyGeo
  • 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.40.0/212,048MF-GNOC-STF-20180613Metropolitan branch of OJSC MegaFon AS25159 178.176.40.0/21LIR-PARTITIONED PAJun 13, 2018abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.176.44.0/221,024Metropolitan-branch-of-OJSC-MegaFonunknownASSIGNED PAApr 18, 2025abuse-mailbox@megafon.ru
via MF-GNOC-STF-20180613

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.40.0/21

Routing history

Pattern
Stable
First seen
Jun 2018
Current origin since
Jun 2018 · 8.4 yr
Origin networks
1