LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

80.64.48.0/20

20 residential-proxy exits · 30 days

Wavenet Limited

Announcement
this exact prefix
RPKI valid
Announced by
AS5413
Type
Business

Residential-proxy exits

Proxy exits
20
0.49% of its addresses · 30 days
Always-on exits
1
5.0% of its exits
Spread
9 of 16
/24s with at least one exit
Providers
50
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.64.54.0/2412
80.64.51.0/2405
80.64.52.0/2404
80.64.61.0/2403
80.64.56.0/2402
80.64.50.0/2401
80.64.53.0/2401
80.64.59.0/2401
80.64.62.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • NextProxy
  • NovProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

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
80.64.48.0/204,096UK-WAVENET-20040122Wavenet Limited (ORG-WTL1-RIPE) · GBALLOCATED PAAug 5, 2025abuse@wavenet.co.uk
└ 80.64.48.0/24256CC-COREControlCircle Core NetworkASSIGNED PAFeb 7, 2007abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.49.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.49.96/298CC-COREControlCircle Core NetworkASSIGNED PAJul 28, 2009abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.50.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.50.0/298CC-COREControlCircle Core NetworkASSIGNED PAOct 25, 2011abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.50.16/298CC-JJohnstonJJohnstonASSIGNED PANov 10, 2014abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.50.128/304CC-4CG4CG GroupASSIGNED PAOct 4, 2012abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.50.176/2816CC-RRDRRDASSIGNED PAMay 6, 2008abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.51.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.51.16/2816CC-WHITTINGTONWhittingtonASSIGNED PADec 15, 2010abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.51.32/2816CC-LarkLarkASSIGNED PASep 15, 2014abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.51.64/2816CC-WiggleWiggleASSIGNED PAJun 12, 2013abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.51.96/2816CC-RRDRRDASSIGNED PAOct 27, 2009abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.51.128/2664CC-CapitalsupportCapitalsupportASSIGNED PAMar 6, 2009abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.52.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.52.88/298CC-AlternativeNetworksAlternative NetworksASSIGNED PAOct 13, 2015abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.52.96/2816CC-RRDRRDASSIGNED PAOct 27, 2009abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.53.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.54.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.55.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 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
└ 80.64.57.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.57.152 - 80.64.57.23180CC-SITECONFIDENCESite ConfidenceASSIGNED PAOct 17, 2011abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.57.232/298CC-WHITTINGTONWhittingtonASSIGNED PANov 16, 2010abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.57.240/298CC-RSPCARSPCAASSIGNED PANov 18, 2010abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.58.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.59.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.59.32/298CC-CoreControlCircleASSIGNED PAMar 16, 2011abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.59.64/2664CC-CapitalsupportCapitalsupportASSIGNED PAJun 10, 2011abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.60.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.61.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.61.128/2664CC-CapitalsupportCapitalsupportASSIGNED PAFeb 17, 2009abuse@wavenet.co.uk
via WAVENET-LIMITED
└ 80.64.62.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.63.0/24256WAVENET-LIMITEDWavenet LimitedLIR-PARTITIONED PAApr 8, 2024abuse@wavenet.co.uk
via UK-WAVENET-20040122
└ 80.64.63.176/2816CC-WHITTINGTONWhittingtonASSIGNED PAMar 8, 2011abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

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