Data as of Nov 13, 2026

81.18.0.0/20

83 residential-proxy exits · 30 days

Cablenet Communication Systems plc

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
30 / 100 · Medium
Recently moved
Recent change
New origin Jun 2026
from AS20867 Sopra Steria Nederland B.V., after 5.5 years unannounced

Residential-proxy exits

Proxy exits
83
2.0% of its addresses · 30 days
Always-on exits
2
2.4% of its exits
Spread
12 of 16
/24s with at least one exit
Providers
80
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

16K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PrivateByte
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.18.0.0/204,096CY-CABLENET-20020114Cablenet Communication Systems plc (ORG-CCSL13-RIPE) · CYALLOCATED PAJun 25, 2026abuse@cablenetcy.net
└ 81.18.0.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.1.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.2.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.3.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.4.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.5.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.6.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.7.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.8.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.9.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.10.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.11.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.12.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.13.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.14.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114
└ 81.18.15.0/24256CUSTOMER-ALLOCATIONS-SHAREDunknownASSIGNED PAJun 25, 2026abuse@cablenetcy.net
via CY-CABLENET-20020114

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
Reactivated
First seen
May 2005
Current origin since
Jun 2026 · 5 mo
Origin networks
2
Last change of origin
Jun 2026
Recorded history

History

Handoffs
1