Data as of Nov 14, 2026

212.48.150.136/29

No anonymizer space · no proxy exits in 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
13
100% of its addresses · listed by providers
Always-on exits
3
23% of its exits
Providers
46
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • APROXY
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXY_CC
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.48.128.0/19
since Apr 2012
AS12714Mobile88
12 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.48.128.0/198,192RU-MEGAFON-980414PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PADec 17, 2001abuse-mailbox@megafon.ru
└ 212.48.150.136/298DILIGENCE-NETNetwork of Diligence+ LTDASSIGNED PANov 3, 2009abuse-mailbox@megafon.ru
via RU-MEGAFON-980414

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

212.48.150.0/24

Routing history

Pattern
Rotating
First seen
May 2025
Current origin since
Nov 2025 · 1.0 yr
Origin networks
2
Last change of origin
Nov 2025
Recorded history

History

Handoffs
1