Data as of Nov 21, 2026

84.204.145.48/30

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Providers
40
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

47 observations

Proxy providers listing exits

  • 2Captcha
  • 911Proxy
  • 9HTTP
  • AETHYN_ELITE
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPFly
  • Infatica
  • LUMIPROXY
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.204.0.0/16
since Feb 2020
AS31133Mobile126
10 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.204.0.0/1665,536RU-MEGAFON-20040609PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAJun 9, 2004abuse-mailbox@megafon.ru
└ 84.204.145.48/304MAYMAKS-DOM-INT-LANMAYMAKSANSKI DOM-INTERNAT networkASSIGNED PAJul 11, 2017abuse-mailbox@megafon.ru
via RU-MEGAFON-20040609

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

84.204.144.0/20

Routing history

Pattern
Stable
First seen
Sep 2006
Current origin since
Aug 2016 · 10 yr
Origin networks
1