Data as of Nov 16, 2026

178.178.216.0/21

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
18
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

411 observations

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • HideProxy
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.176.0.0/14
since Feb 2020
AS31133Mobile30,797
278 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.178.208.0/204,096MF-GDC-20240228-T4816421unknownLIR-PARTITIONED PAFeb 28, 2024abuse-mailbox@megafon.ru
via RU-MEGAFON-20100122
└ 178.178.216.0/212,048MF-MB-20240229unknownASSIGNED PAFeb 29, 2024abuse-mailbox@megafon.ru
via MF-GDC-20240228-T4816421

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