Data as of Nov 20, 2026

81.95.160.0/20

6 residential-proxy exits · 30 days

Magticom Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
6
0.15% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
3 of 16
/24s with at least one exit
Providers
38
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.95.161.0/2414
81.95.160.0/2401
81.95.169.0/2401

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • BottingTools
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • KindProxy
  • LudaxProxy
  • NSTPROXY_PRIME
  • NextProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • Proxy302
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SwiftProxy
  • Thordata
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.95.160.0/21
since May 2005
AS25249Residential5
1 always on
Magticom Ltd.
81.95.160.0/24
since Jul 2007
AS25249Residential1Magticom Ltd.

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
81.95.160.0/204,096GE-MAGTICOM-20020906Magticom Ltd. (ORG-ML2-RIPE) · GEALLOCATED PASep 6, 2002abuse@magtinet.ge
└ 81.95.160.0/221,024GE-MAGTICOMMagticom Ltd.ASSIGNED PAOct 10, 2002abuse@magtinet.ge
via GE-MAGTICOM-20020906
└ 81.95.164.0/221,024GE-MAGTICOMPROVIDERASSIGNED PAJun 21, 2004abuse@magtinet.ge
via GE-MAGTICOM-20020906
└ 81.95.168.0/212,048GE-MAGTICOMMagticom Ltd.ASSIGNED PAFeb 26, 2008abuse@magtinet.ge
via GE-MAGTICOM-20020906

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
May 2005 · 22 yr
Origin networks
1