Data as of Nov 16, 2026

188.170.185.0/24

3 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
3
1.2% of its addresses · 30 days
Providers
24
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.170.0.0/16
since Mar 2020
AS31133Mobile7,162
33 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.176.0/204,096MF-KF-20170314Mobile & Fixed Broadband - Caucasus Branch of OJSC MegaFon AS31163 188.170.176.0/20LIR-PARTITIONED PAMar 14, 2017abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.185.0/24256MF-KAVKAZ-18082022-T4122797unknownASSIGNED PAMar 16, 2017abuse-mailbox@megafon.ru
via MF-KF-20170314

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