Data as of Nov 22, 2026

217.46.139.0/24

7 residential-proxy exits · 30 days

British Telecommunications Limited

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
24
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

219 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • FastProxy
  • GEEKPROXY_TURBO
  • GoProxies
  • IPMUSK
  • IPPeak
  • IPRoyal
  • KindProxy
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyWing
  • Q2IP
  • ThunderProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.32.0.0/12
since May 2005
AS2856Residential17,730
555 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
217.32.0.0/121,048,576UK-BT-20000920British Telecommunications Limited (ORG-BPIS1-RIPE) · GBALLOCATED PASep 10, 2002abuse@bt.com
└ 217.40.0.0/13524,288BT-INFRABT Infrastructure LayerLIR-PARTITIONED PAAug 1, 2014abuse@bt.com
via UK-BT-20000920
└ 217.46.128.0/204,096PlusnetPlusnet PLCSUB-ALLOCATED PAJul 16, 2015abuse@bt.com
via BT-INFRA
└ 217.46.136.0/212,048PLUSNET-ADSL-26Plusnet PLCASSIGNED PAAug 27, 2015abuse@bt.com
via Plusnet

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

217.46.128.0/20

Routing history

Pattern
Stable
First seen
Aug 2015
Current origin since
Aug 2015 · 11 yr
Origin networks
1