Data as of Nov 17, 2026

212.159.32.0/19

18 residential-proxy exits · 30 days

British Telecommunications Limited

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

Residential-proxy exits

Proxy exits
18
0.22% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
7 of 32
/24s with at least one exit
Providers
68
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

18K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXORA
  • PROXYON
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.159.0.0/17
since Jun 2026
AS6871Residential183
30 always on
British Telecommunications Limited

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.159.0.0/1732,768UK-BT-990412British Telecommunications Limited (ORG-BPIS1-RIPE) · GBALLOCATED PAOct 5, 2016abuse@bt.com
└ 212.159.32.0/23512PLUSNET-DIAL-ADSLADSL poolASSIGNED PADec 7, 2009abuse@bt.com
via UK-BT-990412
└ 212.159.34.0/23512PLUSNET-DIAL-FRIACOFRIACO Dial-up poolASSIGNED PASep 9, 2003abuse@bt.com
via UK-BT-990412
└ 212.159.36.0/23512PLUSNET-DIAL-ADSLADSL poolASSIGNED PADec 7, 2009abuse@bt.com
via UK-BT-990412
└ 212.159.38.0/23512PLUSNET-DIAL-FRIACOFRIACO Dial-up poolASSIGNED PASep 9, 2003abuse@bt.com
via UK-BT-990412
└ 212.159.42.0/23512PLUSNET-DIAL-ADSLDial-up and ADSL poolASSIGNED PASep 9, 2003abuse@bt.com
via UK-BT-990412
└ 212.159.44.0/221,024PLUSNET-DIAL-ADSLDial-up and ADSL poolASSIGNED PASep 9, 2003abuse@bt.com
via UK-BT-990412
└ 212.159.48.0/204,096PLUSNET-DIAL-ADSLDial-up and ADSL poolASSIGNED PADec 7, 2009abuse@bt.com
via UK-BT-990412

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

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1