Data as of Nov 14, 2026

188.170.136.0/24

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
4
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3 observations

Proxy providers listing exits

  • Geonix
  • IPFly
  • PuraRoute
  • Shifter

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.134.0 - 188.170.143.2552,560MF-VLGunknownLIR-PARTITIONED PASep 15, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20090624
└ 188.170.136.0/24256MF-PF-20220809unknownLIR-PARTITIONED PAAug 9, 2022abuse-mailbox@megafon.ru
via MF-VLG
└ 188.170.136.0/25128MF-PF-FixunknownASSIGNED PAAug 11, 2023abuse-mailbox@megafon.ru
via MF-PF-20220809
└ 188.170.136.128/25128MF-PF-FixunknownASSIGNED PAAug 11, 2023abuse-mailbox@megafon.ru
via MF-PF-20220809

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
Apr 2018
Current origin since
Apr 2018 · 8.6 yr
Origin networks
1