Data as of Nov 10, 2026

86.2.176.0/24

5 residential-proxy exits · 30 days

Virgin Media Limited

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
30
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.0.0.0/13
since Aug 2016
AS5089Residential11,676
2,165 always on
Virgin Media Limited
86.0.0.0/11
since May 2005
AS5089Residential50,908
9,642 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
86.0.0.0/112,097,152UK-NTLI-20050329Virgin Media Limited (ORG-NI9-RIPE) · GBALLOCATED PAMar 29, 2005abuse@virginmediao2.co.uk
└ 86.2.176.0/204,096VMCBBUKunknownASSIGNED PAFeb 13, 2024abuse@virginmediao2.co.uk
via UK-NTLI-20050329

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

86.0.0.0/14

Routing history

Pattern
Stable
First seen
Dec 2011
Current origin since
Aug 2016 · 10 yr
Origin networks
1