Data as of Nov 10, 2026

86.63.0.0/19

12 residential-proxy exits · 30 days

WightFibre Limited

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

Residential-proxy exits

Proxy exits
12
0.15% of its addresses · 30 days
Always-on exits
2
17% of its exits
Spread
6 of 32
/24s with at least one exit
Providers
52
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

21K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.63.0.0/18
since Nov 2018
AS60426Residential57
11 always on
WightFibre Limited

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
86.63.0.0/1816,384UK-WIGHTCABLE-20050616WightFibre Limited (ORG-WL13-RIPE) · GBALLOCATED PAJun 16, 2005abuse@wightfibre.com
└ 86.63.0.0/23512Wightfibre-InfrastructureWightfibre LtdASSIGNED PAApr 29, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.3.0/24256Wightfibre-WirelessWireless CustomersASSIGNED PAApr 29, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.4.0/23512Wightfibre-CableCable ModemsASSIGNED PAApr 29, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.6.0/24256Wightfibre_Leased_LineLeased Line CustomersASSIGNED PAJun 22, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.7.0/24256Wightfibre-InfrastructureunknownASSIGNED PAJul 14, 2022abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.8.0/24256Wightfibre_Leased_LineLeased Line CustomersASSIGNED PAJun 22, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.9.0/24256Wightfibre_Leased_LineLeased Line CustomersASSIGNED PAJun 22, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.10.0/24256Wightfibre-InfrastructureunknownASSIGNED PAJul 14, 2022abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.12.0/23512Wightfibre-InfrastructureWireless CustomersASSIGNED PAApr 29, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616
└ 86.63.14.0/23512Wightfibre-InfrastructureWireless CustomersASSIGNED PAApr 29, 2015abuse@wightfibre.com
via UK-WIGHTCABLE-20050616

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

Summary

Routing history

Pattern
Stable
First seen
Feb 2026
Current origin since
Feb 2026 · 9 mo
Origin networks
1