Data as of Nov 20, 2026

188.170.236.0/24

1 residential-proxy exit · 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
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

99 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FloppyData
  • GEEKPROXY_FLEX
  • GonzoProxy
  • Infatica
  • LightningProxies
  • NodeMaven
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.170.0.0/16
since Mar 2020
AS31133Mobile7,196
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.228.0 - 188.170.239.2553,072MF-DVFFar East Branch of PJSC MegaFonLIR-PARTITIONED PAJul 7, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.236.0/24256MF-GNOC-DF-20180903Far East Branch of PJSC MegaFonASSIGNED PASep 3, 2018abuse-mailbox@megafon.ru
via MF-DVF

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 2009
Current origin since
Aug 2018 · 8.3 yr
Origin networks
2
Last change of origin
Aug 2018
Recorded history

History

Handoffs
1