Data as of Nov 12, 2026

80.64.56.0/24

2 residential-proxy exits · 30 days

Wavenet Limited

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
14
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

62 observations

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • FastProxy
  • Geonode
  • HideProxy
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • ProxiesVision
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ThunderProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.64.48.0/204,096UK-WAVENET-20040122Wavenet Limited (ORG-WTL1-RIPE) · GBALLOCATED PAAug 5, 2025abuse@wavenet.co.uk
└ 80.64.56.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.56.176/2816CC-RRDRRDASSIGNED PAAug 22, 2008abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.56.192/2816CC-RRDRRDASSIGNED PAMay 6, 2008abuse@wavenet.co.uk
via WAVENET-LIMITED

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 80.64.48.0/20

80.64.48.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2020 · 6.4 yr
Origin networks
2
Last change of origin
Jun 2020
Recorded history

History

Handoffs
1