Data as of Nov 13, 2026

83.169.253.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
22
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

171 observations

Proxy providers listing exits

  • 2Captcha
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • Evomi
  • FloppyData
  • GonzoProxy
  • IPCola
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.169.192.0/18
since Feb 2020
AS31133Mobile348
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.252.0/221,024PS-Core-APN-publicSIBunknownASSIGNED PAOct 2, 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.252.0/22

Routing history

Pattern
Stable
First seen
Feb 2014
Current origin since
Feb 2014 · 13 yr
Origin networks
1