Data as of Nov 14, 2026

188.170.166.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
Always-on exits
2
100% of its exits
Providers
22
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • Kookey
  • Maskify
  • NSocks
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma

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.160.0/212,048MF-GNOC-PF-20171006PJSC MegaFon (ORG-OM1-RIPE) · RULIR-PARTITIONED PAOct 6, 2017abuse-mailbox@megafon.ru
└ 188.170.164.0/221,024MF-MC-20072022unknownASSIGNED PAJul 20, 2022abuse-mailbox@megafon.ru
via MF-GNOC-PF-20171006

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
Oct 2017
Current origin since
Aug 2022 · 4.2 yr
Origin networks
1