Data as of Nov 20, 2026

212.56.100.0/23

3 residential-proxy exits · 30 days

British Telecommunications Limited

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

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
36
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

3.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.56.101.0/2412
212.56.100.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FROXY
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GonzoProxy
  • IP2WORLD
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.56.64.0/1816,384UK-BT-980608British Telecommunications Limited (ORG-BPIS1-RIPE) · GBALLOCATED PAOct 5, 2016abuse@bt.com
└ 212.56.100.0/23512PLUSNET-DIAL-ADSLPlusNet Technologies LtdASSIGNED PASep 9, 2003abuse@bt.com
via UK-BT-980608

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

Who has announced 212.56.64.0/18

212.56.64.0/18

Routing history

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