Data as of Nov 14, 2026

188.170.63.0/24

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

88 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.170.0.0/16
since Mar 2020
AS31133Mobile7,143
34 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.170.0.0/1665,536RU-MEGAFON-20090624PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAOct 16, 2014abuse-mailbox@megafon.ru
└ 188.170.59.0 - 188.170.63.2551,280MF-CENTER-188-170-56Center Branch of OJSC MegaFon, FBB11LIR-PARTITIONED PAMar 22, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.63.0/24256MF-CF-07072022unknownASSIGNED PAJul 7, 2022abuse-mailbox@megafon.ru
via MF-CENTER-188-170-56

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