Data as of Nov 18, 2026

46.229.128.0/21

4 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
4
0.20% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
3
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

226 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

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
46.229.128.0/22
since Jul 2011
AS25159Mobile4
1 always on
PJSC MegaFon
46.229.132.0/22
since Jul 2011
AS31224MobilePJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each 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
└ 46.229.132.0/221,024MF-GDC-20210810-T3693071Ural Branch of OJSC MegaFon GPRS/UMTS Network, Pool 3ASSIGNED PAJun 24, 2011abuse-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

Who has announced 46.229.128.0/20

46.229.128.0/20

Routing history

Pattern
Stable
First seen
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1