Data as of Nov 12, 2026

86.154.155.0/24

28 residential-proxy exits · 30 days

British Telecommunications Limited

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

Residential-proxy exits

Proxy exits
28
11% of its addresses · 30 days
Always-on exits
3
11% of its exits
Providers
63
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

19K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.128.0.0/10
since May 2005
AS2856Residential237,333
6,394 always on
British Telecommunications Limited

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.128.0.0/104,194,304UK-BT-20050207British Telecommunications Limited (ORG-BPIS1-RIPE) · GBALLOCATED PAFeb 7, 2005abuse@bt.com
└ 86.128.0.0/112,097,152BT-INFRABT Infrastructure LayerLIR-PARTITIONED PAAug 1, 2014abuse@bt.com
via UK-BT-20050207
└ 86.148.0.0 - 86.159.255.255786,432BT-CENTRAL-PLUSIP poolsASSIGNED PANov 1, 2006abuse@bt.com
via BT-INFRA

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.128.0.0/11

Routing history

Pattern
Stable
First seen
Nov 2010
Current origin since
Nov 2010 · 16 yr
Origin networks
1