Data as of Nov 13, 2026

188.170.131.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
Always-on exits
1
33% of its exits
Providers
28
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.170.0.0/16
since Mar 2020
AS31133Mobile7,151
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.131.0 - 188.170.132.255512MF-VLGunknownLIR-PARTITIONED PASep 15, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.131.0/24256MF-PF-20220808unknownASSIGNED PAAug 8, 2022abuse-mailbox@megafon.ru
via MF-VLG

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
Sep 2017
Current origin since
Sep 2017 · 9.2 yr
Origin networks
1