Data as of Nov 21, 2026

104.200.108.0/23

18 residential-proxy exits · 30 days

Columbus Telecommunications (Barbados) Limited

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

Residential-proxy exits

Proxy exits
18
3.5% of its addresses · 30 days
Always-on exits
4
22% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
42
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

15K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
104.200.109.0/2449
104.200.108.0/2409

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • GonzoProxy
  • IP2WORLD
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • LITPORT_LIMA
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYON
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • ProxyEmpire
  • ProxyWing
  • Proxying
  • Q2IP
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
104.200.96.0/20
since Oct 2014
AS14813Residential746
93 always on
Columbus Telecommunications (Barbados) 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
104.200.96.0/204,096COL-BB-5Columbus Telecommunications (Barbados) Limited (CTBL) · BBDirect AllocationOct 2, 2014cwc-csirt@cwc.com
└ 104.200.108.0/24256COL-BB-5Columbus-Garrison FTTH #4 (C05605222) · BBReassignedFeb 20, 2015cwc-csirt@cwc.com
via COL-BB-5
└ 104.200.109.0/24256COL-BB-5Columbus-Maynards FTTH #1 (C05605230) · BBReassignedFeb 20, 2015cwc-csirt@cwc.com
via COL-BB-5

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
Nov 2016
Current origin since
Nov 2016 · 10 yr
Origin networks
1