Data as of Nov 21, 2026

83.169.250.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

386 observations

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.169.192.0/18
since Feb 2020
AS31133Mobile353
20 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.169.192.0/1816,384RU-MEGAFON-20040420PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAApr 20, 2004abuse-mailbox@megafon.ru
└ 83.169.248.0/212,048MF-SF-GDCunknownLIR-PARTITIONED PANov 9, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20040420
└ 83.169.248.0/221,024PSCore-APN-public-sibunknownASSIGNED PAJan 25, 2023abuse-mailbox@megafon.ru
via MF-SF-GDC

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

83.169.248.0/22

Routing history

Pattern
Stable
First seen
Dec 2014
Current origin since
Dec 2014 · 12 yr
Origin networks
1