Data as of Nov 10, 2026

80.3.0.0/17

1,053 residential-proxy exits · 30 days

Virgin Media Limited

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1,053
3.2% of its addresses · 30 days
Always-on exits
217
21% of its exits
Spread
115 of 128
/24s with at least one exit
Providers
116
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

908K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • MrScraper
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.2.0.0/15
since Aug 2016
AS5089Residential3,963
814 always on
Virgin Media Limited
80.0.0.0/13
since May 2005
AS5089Residential15,564
3,138 always on
Virgin Media Limited

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.0.0.0/13524,288UK-NTLI-20010425Virgin Media Limited (ORG-NI9-RIPE) · GBALLOCATED PAApr 23, 2002abuse@virginmediao2.co.uk
└ 80.3.1.0/24256VMCBBUKMAPPERLEYASSIGNED PAJun 24, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.4.0/221,024VMCBBUKAztec WestASSIGNED PAApr 29, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.8.0/212,048VMCBBUKSALISBURYASSIGNED PAJun 9, 2023abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.20.0/221,024VMCBBUKCARDIFFASSIGNED PAJul 17, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.24.0/221,024VMCBBUKCAMBRIDGEASSIGNED PAJul 17, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.28.0/23512VMCBBUKSouth GyleASSIGNED PAJun 12, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.30.0/24256VMCBBUKMAPPERLEYASSIGNED PAJun 24, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.31.0/24256VMCBBUKBAGULEYASSIGNED PAFeb 4, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.33.0/24256VMCBBUKMAPPERLEYASSIGNED PAJun 24, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.36.0/221,024VMCBBUKDUNSTABLEASSIGNED PAJul 17, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.40.0/212,048VMCBBUKSHEPSHEDASSIGNED PAFeb 4, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.48.0/204,096VMCBBUKLICHFIELDASSIGNED PAJul 25, 2022abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.66.0/23512VMCBBUKCAMBRIDGEASSIGNED PASep 22, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.68.0/221,024VMCBBUKDUNSTABLEASSIGNED PAJul 17, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.72.0/212,048VMCBBUKSUNDERLANDASSIGNED PAFeb 4, 2025abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.80.0/212,048VMCBBUKCOSHAMASSIGNED PAOct 2, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.88.0/221,024VMCBBUKBASFORDASSIGNED PAJul 19, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.92.0/221,024VMCBBUKCHESTERFIELDASSIGNED PAMar 24, 2026abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.100.0/221,024VMCBBUKHemel HempsteadASSIGNED PAJul 17, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.104.0/212,048VMCBBUKTILBURYASSIGNED PAOct 16, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20010425
└ 80.3.112.0/204,096VMCBBUKBOLTONASSIGNED PAJul 25, 2022abuse@virginmediao2.co.uk
via UK-NTLI-20010425

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

80.3.0.0/16

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2016 · 10 yr
Origin networks
1