Data as of Nov 12, 2026

166.49.128.0/17

18 residential-proxy exits · 30 days

British Telecommunications Limited · space held by communications networking services Private Unlimited Company

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
>99% of it

Residential-proxy exits

Proxy exits
18
0.05% of its addresses · 30 days
Always-on exits
1
5.6% of its exits
Spread
14 of 128
/24s with at least one exit
Providers
30
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GoProxies
  • GonzoProxy
  • Infatica
  • LemonBright
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • Webshare

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
166.49.128.0/1732,768BT-IGNITE-GLOBAL-BACKBONEcommunications networking services Private Unlimited Company (ORG-CNS54-RIPE) · GBLEGACYJul 9, 2003ipadmin@bt.com
└ 166.49.128.0/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 18, 2022abuse@eu.bt.net
└ 166.49.128.104/298COMPUTACENTERCOMPUTACENTERLEGACYNov 8, 2025abuse@eu.bt.net
via BT_AS5400_CC41_WB
└ 166.49.129.0/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.130.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.131.128/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.132.0/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.133.0/24256BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 19, 2017abuse@eu.bt.net
└ 166.49.134.0/25128BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJan 8, 2018abuse@eu.bt.net
└ 166.49.134.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.137.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.138.0/25128BT_AS5400_CC34_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJun 14, 2023abuse@eu.bt.net
└ 166.49.138.100/312KANTAR_GROUPunknownLEGACYJun 14, 2023abuse@eu.bt.net
via BT_AS5400_CC34_WB
└ 166.49.138.232/298COMPUTACENTERCOMPUTACENTERLEGACYNov 8, 2025ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.139.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.139.128/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.140.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYFeb 15, 2023abuse@eu.bt.net
└ 166.49.140.128/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.142.0/24256BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.145.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.146.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYFeb 15, 2023abuse@eu.bt.net
└ 166.49.146.128/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.147.24/298COMPUTACENTERCOMPUTACENTERLEGACYNov 8, 2025ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.147.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.148.64/2664BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.148.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.149.0/25128BT_AS5400_CC353_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJul 6, 2022abuse@eu.bt.net
└ 166.49.149.128/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.150.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYFeb 15, 2023abuse@eu.bt.net
└ 166.49.150.128/25128BT_AS5400_CC353_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYApr 19, 2023abuse@eu.bt.net
└ 166.49.151.0/25128BT_AS5400_CC420_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 19, 2018abuse@eu.bt.net
└ 166.49.153.128/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.154.0/24256BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.155.0/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.155.128/25128BT_AS5400_CC36_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 11, 2022abuse@eu.bt.net
└ 166.49.155.142/312INDESIT_COMPANY_SPAIndesit Company SPALEGACYJun 22, 2022abuse@eu.bt.net
via BT_AS5400_CC36_WB
└ 166.49.157.0/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYSep 23, 2019abuse@eu.bt.net
└ 166.49.157.128/25128BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 19, 2017abuse@eu.bt.net
└ 166.49.159.0/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJun 18, 2014abuse@eu.bt.net
└ 166.49.159.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.160.128/25128BT_AS5400_CC45_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.160.230/312BT_AS5400_CC46_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJan 28, 2025abuse@eu.bt.net
└ 166.49.161.0/24256BT-IGNITE-GLOBAL-BACKBONECommunications Networking ServicesLEGACYJul 8, 2021ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.161.2/312INDESIT_COMPANY_SPAIndesit Company SPALEGACYJun 22, 2022ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.162.128/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.167.0/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 18, 2022abuse@eu.bt.net
└ 166.49.168.0/25128BT_AS5400_CC45_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.173.128/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 18, 2022abuse@eu.bt.net
└ 166.49.183.0/24256BT_AS5400_CC420_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 19, 2018abuse@eu.bt.net
└ 166.49.189.0/25128BT_AS5400_CC358_WBunknownLEGACYOct 19, 2022ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.189.128/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.191.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.192.0/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYFeb 1, 2018abuse@eu.bt.net
└ 166.49.192.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.193.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.196.0/24256BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 19, 2017abuse@eu.bt.net
└ 166.49.197.0/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 18, 2022abuse@eu.bt.net
└ 166.49.198.0/25128BT_AS5400_CC353_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYApr 19, 2023abuse@eu.bt.net
└ 166.49.198.128/25128BT_AS5400_CC353_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYApr 19, 2023abuse@eu.bt.net
└ 166.49.210.0/24256BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.211.0/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJun 28, 2022abuse@eu.bt.net
└ 166.49.212.0/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.215.0/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.215.128/25128BT_AS5400_CC43_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.216.0/24256BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.217.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.219.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.220.0/25128BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 19, 2017abuse@eu.bt.net
└ 166.49.221.0/24256BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.222.0/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.222.128/25128BT_AS5400_CC43_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJan 25, 2017abuse@eu.bt.net
└ 166.49.223.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.224.128/25128BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJan 8, 2018abuse@eu.bt.net
└ 166.49.225.128/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.226.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.227.128/25128BT_AS5400_CC34_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJun 14, 2023abuse@eu.bt.net
└ 166.49.227.172/312KANTAR_GROUPBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJun 14, 2023abuse@eu.bt.net
└ 166.49.228.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.229.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.230.0/24256BT-IGNITE-GLOBAL-BACKBONECommunications Networking ServicesLEGACYMay 9, 2018ipadmin@bt.com
via BT-IGNITE-GLOBAL-BACKBONE
└ 166.49.233.0/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.233.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.234.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYFeb 15, 2023abuse@eu.bt.net
└ 166.49.234.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.235.0/25128BT_AS5400_CC32_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYJan 8, 2018abuse@eu.bt.net
└ 166.49.238.0/24256BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.238.0/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 1, 2022abuse@eu.bt.net
└ 166.49.239.0/25128BT_AS5400_CC33_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net
└ 166.49.239.72/298COMPUTACENTERCOMPUTACENTERLEGACYNov 8, 2025abuse@eu.bt.net
via BT_AS5400_CC33_WB
└ 166.49.239.128/25128BT_AS5400_CC31_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYDec 14, 2017abuse@eu.bt.net
└ 166.49.242.0/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.242.128/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.243.0/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.243.128/25128BT_AS5400_CC39_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 24, 2022abuse@eu.bt.net
└ 166.49.251.0/25128BT_AS5400_CC41_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYNov 18, 2022abuse@eu.bt.net
└ 166.49.251.128/25128BT_AS5400_CC49_WBBritish Telecommunications Limited (ORG-CNS3-RIPE) · GBLEGACYMar 22, 2023abuse@eu.bt.net

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

32,768 addresses
TypeAddressesShareRanges
Unknown32,602>99%9
Business1660.51%8

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2016 · 10 yr
Origin networks
1