Data as of Nov 21, 2026

188.162.246.0/23

2 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
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
14
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

13 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • EnigmaProxy
  • FloppyData
  • IPFly
  • Novada
  • Oxylabs
  • ProxyWing
  • PuraRoute
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.162.0.0/16
since Mar 2020
AS31133Mobile18,826
8 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.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.246.0/23512DVF_Khabarovsk_YOTA-mobileDVF Khabarovsk YOTA-mobileASSIGNED PAMar 5, 2015abuse-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

Summary

Routing history

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

History

Handoffs
1