Data as of Nov 18, 2026

217.32.113.0/24

16 residential-proxy exits · 30 days

British Telecommunications Limited

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

Residential-proxy exits

Proxy exits
16
6.3% of its addresses · 30 days
Always-on exits
1
6.3% of its exits
Providers
56
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

13K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • GhostConnect
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • TrueProxies
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.32.0.0/12
since May 2005
AS2856Residential17,635
481 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.32.0.0/13524,288BT-INFRABT Infrastructure LayerLIR-PARTITIONED PAAug 1, 2014abuse@bt.com
via UK-BT-20000920
└ 217.32.112.0/221,024PlusnetPlusnet PLCSUB-ALLOCATED PAJul 16, 2015abuse@bt.com
via BT-INFRA
└ 217.32.112.0/23512PLUSNET-ADSL-31Plusnet 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.32.112.0/22

Routing history

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