Data as of Nov 15, 2026

46.229.128.0/22

4 residential-proxy exits · 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
4
0.39% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
3
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

209 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.229.129.0/2412
46.229.128.0/2401
46.229.131.0/2401

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.229.128.0/20
since Feb 2020
AS31133Mobile29
3 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
46.229.128.0/204,096RU-MEGAFON-20110217PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAFeb 17, 2011abuse-mailbox@megafon.ru
└ 46.229.128.0/212,048MF-MOSCOW-GDCunknownLIR-PARTITIONED PAJul 18, 2023abuse-mailbox@megafon.ru
via RU-MEGAFON-20110217
└ 46.229.128.0/221,024APN-fixedIPunknownASSIGNED PAApr 17, 2025abuse-mailbox@megafon.ru
via MF-MOSCOW-GDC

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
Jul 2011
Current origin since
Jul 2011 · 15 yr
Origin networks
1