Data as of Nov 11, 2026

147.152.0.0/16

4 residential-proxy exits · 30 days

British Telecommunications Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
76% of it

Residential-proxy exits

Proxy exits
4
<0.01% of its addresses · 30 days
Spread
1 of 256
/24s with at least one exit
Providers
19
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

9 observations

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • ByteProxies
  • Byteful
  • DataImpulse
  • FloppyData
  • GonzoProxy
  • IPFly
  • Infatica
  • Kookey
  • LightningProxies
  • MangoProxy
  • PSBProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • VitalExclusive
  • VitalProxy

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
147.147.0.0 - 147.152.255.255393,216BTBritish Telecommunications Limited (ORG-BT4-RIPE) · GBLEGACYJan 18, 2012protect@bt.com
└ 147.152.0.0/212,048BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.8.0/221,024BT-CORPORATEunknownLEGACYJul 25, 2012protect@bt.com
via BT
└ 147.152.12.0/23512BT-CORPORATEunknownLEGACYJul 25, 2012protect@bt.com
via BT
└ 147.152.14.0/24256BT-CORPORATEunknownLEGACYJul 25, 2012protect@bt.com
via BT
└ 147.152.15.0/24256BT-CORPORATEunknownLEGACYJul 26, 2012protect@bt.com
via BT
└ 147.152.16.0/24256BT-CORPORATEFrance AOLEGACYAug 21, 2012protect@bt.com
via BT
└ 147.152.17.0/24256BT-CORPORATESDINLEGACYApr 15, 2013protect@bt.com
via BT
└ 147.152.18.0/25128BT-CORPORATEHVSLEGACYMay 24, 2013protect@bt.com
via BT
└ 147.152.18.128/2664BT-CORPORATEunknownLEGACYJun 12, 2013protect@bt.com
via BT
└ 147.152.18.192/2732BT-CORPORATEFTIP003312209LEGACYJul 2, 2013protect@bt.com
via BT
└ 147.152.18.224/2816BT-CORPORATEHVSLEGACYMar 28, 2013protect@bt.com
via BT
└ 147.152.21.0/24256BT-CORPORATECACSLEGACYMay 28, 2013protect@bt.com
via BT
└ 147.152.22.0/25128BT-CORPORATEunknownLEGACYMay 29, 2013protect@bt.com
via BT
└ 147.152.22.128/2664BT-CORPORATEBTINFRALEGACYSep 20, 2013protect@bt.com
via BT
└ 147.152.22.192/2732BT-CORPORATEHGPLEGACYAug 8, 2014protect@bt.com
via BT
└ 147.152.23.0/25128BT-CORPORATEunknownLEGACYJun 26, 2013protect@bt.com
via BT
└ 147.152.23.128/2664BT-CORPORATESBCLEGACYAug 20, 2013protect@bt.com
via BT
└ 147.152.23.224/2732BT-CORPORATEGHUCSLEGACYDec 16, 2013protect@bt.com
via BT
└ 147.152.24.0/212,048BT-CORPORATEIPCONVERGELEGACYJul 4, 2013protect@bt.com
via BT
└ 147.152.32.0/23512BT-CORPORATEunknownLEGACYAug 1, 2013protect@bt.com
via BT
└ 147.152.34.0/24256BT-CORPORATECISCOHCSLEGACYAug 27, 2013protect@bt.com
via BT
└ 147.152.36.0/221,024BT-CORPORATEBTMPLSLEGACYSep 30, 2013protect@bt.com
via BT
└ 147.152.44.0/23512BT-CORPORATEBTECLEGACYOct 9, 2013protect@bt.com
via BT
└ 147.152.48.0/221,024BT-CORPORATEBTMPLSLEGACYNov 15, 2013protect@bt.com
via BT
└ 147.152.152.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.178.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.184.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.195.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.216.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.232.0/221,024BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.240.0/23512BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.242.0/24256BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.244.0/221,024BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT
└ 147.152.252.0/221,024BT-CORPORATEunknownLEGACYJul 24, 2012protect@bt.com
via BT

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

65,536 addresses
TypeAddressesShareRanges
Residential49,48876%15
Business16,04824%34

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

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