FUTURE CONNECT BROADBAND

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2001:dec:4000::14:7226:1/128)
Also registered under this name 31 netblocks across 2 separate records
Record ID246699055
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.77.108.103/32 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
103.188.179.26/32 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
223.31.200.153/32 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
223.31.200.200/32 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
2001:dec:4000::14:7226:1/128 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
2001:df2:1900:2::1030/128 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
2001:e48:44:100b:a500:14:7226:1/128 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high
2001:e48:44:100b:a500:14:7226:2/128 FUTURE CONNECT BROADBAND PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

7 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-10-04

Network trust

what's this?
RPKI hygiene: D how networks compare →
37.5% of checked blocks have valid RPKI ROA coverage (3 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS147226