Data as of Nov 11, 2026

85.26.199.0/24

9 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
9
3.5% of its addresses · 30 days
Providers
35
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.128.0/17
since Feb 2020
AS31133Mobile3,066
9 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.26.128.0/1732,768RU-MEGAFON-20050310PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMar 10, 2005abuse-mailbox@megafon.ru
└ 85.26.199.0/24256CUSTOMERS-NAT-LANCORPASSIGNED PAJun 27, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310

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

85.26.196.0/22

Routing history

Pattern
Stable
First seen
Mar 2011
Current origin since
Mar 2011 · 16 yr
Origin networks
1