Data as of Nov 21, 2026

188.170.0.0/19

17 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
17
0.21% of its addresses · 30 days
Always-on exits
1
5.9% of its exits
Spread
12 of 32
/24s with at least one exit
Providers
63
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BUYPERSONALPROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • HASDATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LUMIPROXY
  • LudaxProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NovaProxy
  • Oxylabs
  • PROXIES.RIP
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXY_CC
  • PacketStream
  • PrivateByte
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • VantageProxies
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.170.0.0/16
since Mar 2020
AS31133Mobile7,199
35 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.0.0 - 188.170.23.2556,144MF-MOSCOW-BBA-POOLMoscow Branch of OJSC MegaFonLIR-PARTITIONED PAJul 6, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.0.0/204,096MF-STF-21062023unknownSUB-ALLOCATED PAJun 22, 2023abuse-mailbox@megafon.ru
via MF-MOSCOW-BBA-POOL
└ 188.170.16.0/212,048MF-STF-21062023unknownSUB-ALLOCATED PAJun 22, 2023abuse-mailbox@megafon.ru
via MF-MOSCOW-BBA-POOL
└ 188.170.24.0/221,024MF-MC-GDC-YOTAunknownLIR-PARTITIONED PAJul 6, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.24.0/23512MVNO-GAZPROMTELECOMunknownASSIGNED PAApr 17, 2025abuse-mailbox@megafon.ru
via MF-MC-GDC-YOTA
└ 188.170.26.0/23512MVNO-GAZPROMTELECOMunknownASSIGNED PAApr 17, 2025abuse-mailbox@megafon.ru
via MF-MC-GDC-YOTA
└ 188.170.28.0/221,024MF-MOSCOW-BBA-POOLMoscow Branch of OJSC MegaFonLIR-PARTITIONED PAJul 6, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.28.0/23512MF-STF-21062023unknownSUB-ALLOCATED PAJun 22, 2023abuse-mailbox@megafon.ru
via MF-MOSCOW-BBA-POOL
└ 188.170.30.0/23512MF-STF-21062023unknownSUB-ALLOCATED PAJun 22, 2023abuse-mailbox@megafon.ru
via MF-MOSCOW-BBA-POOL

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
Nov 2016
Current origin since
Nov 2016 · 10 yr
Origin networks
1