Data as of Nov 18, 2026

213.200.0.0/19

512 residential-proxy exits · 30 days

Magticom Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
512
6.3% of its addresses · 30 days
Always-on exits
453
88% of its exits
Spread
2 of 32
/24s with at least one exit
Providers
76
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

807K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.200.31.0/24229256
213.200.15.0/24224256

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NovProxy
  • Novada
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.200.0.0/198,192GE-MAGTICOM-20050323Magticom Ltd. (ORG-ML2-RIPE) · GEALLOCATED PAAug 11, 2016abuse@magtinet.ge
└ 213.200.1.0/24256MAGTICOMMAGTCIONASSIGNED PAMar 6, 2009abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.2.0/24256MAGTICOMMAGTCIONASSIGNED PAMar 6, 2009abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.6.0/24256MAGTICOMMAGTCIONASSIGNED PAFeb 22, 2008abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.8.0/24256MAGTICOMMAGTCIONASSIGNED PAOct 1, 2007abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.9.0 - 213.200.10.255512MAGTICOMMAGTCIONASSIGNED PAJun 2, 2009abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.11.0/24256MAGTICOMMAGTCIONASSIGNED PAOct 1, 2007abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.12.0/25128MAGTICOMMAGTCIONASSIGNED PANov 25, 2005abuse@magtinet.ge
via GE-MAGTICOM-20050323
└ 213.200.16.0/204,096MAGTICOMMAGTCIONASSIGNED PAJun 24, 2010abuse@magtinet.ge
via GE-MAGTICOM-20050323

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Dec 2016 · 9.9 yr
Origin networks
4
Last change of origin
Dec 2016
Recorded history

History

Handoffs
4