Data as of Nov 20, 2026

188.162.252.0/24

15 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
23
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

72 observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • B2Proxy
  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • PROXYON
  • ProxiesVision
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.162.0.0/16
since Mar 2020
AS31133Mobile18,793
8 always on
PJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.162.0.0/1665,536RU-MEGAFON-20090520PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMay 20, 2009abuse-mailbox@megafon.ru
└ 188.162.224.0/198,192MF-DVF-T3306070Far East PLSC MegafonSUB-ALLOCATED PAAug 14, 2020abuse-mailbox@megafon.ru
via RU-MEGAFON-20090520
└ 188.162.252.0/221,024DVF_Irkutsk_YOTA-mobileunknownASSIGNED PANov 25, 2020abuse-mailbox@megafon.ru
via MF-DVF-T3306070

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

188.162.252.0/22

Routing history

Pattern
Stable
First seen
Sep 2015
Current origin since
Dec 2020 · 5.9 yr
Origin networks
4
Last change of origin
Dec 2020
Recorded history

History

Handoffs
5