Data as of Nov 14, 2026

188.162.89.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
22
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.162.0.0/16
since Mar 2020
AS31133Mobile18,251
6 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
188.162.0.0/1665,536RU-MEGAFON-20090520PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMay 20, 2009abuse-mailbox@megafon.ru
└ 188.162.64.0/198,192MF-GDC-17072023unknownLIR-PARTITIONED PAJul 17, 2023abuse-mailbox@megafon.ru
via RU-MEGAFON-20090520
└ 188.162.89.0/24256NSK-Yota-clientsunknownASSIGNED PAApr 17, 2025abuse-mailbox@megafon.ru
via MF-GDC-17072023

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
May 2021
Current origin since
May 2021 · 5.5 yr
Origin networks
1