FUSION TELECOM

Data as of 2026-10-18
BGP inherited
This organisation
Netblocks13 · 1,026 IPv4 addresses
IPv6 4 prefixes (largest 2804:6ac8::/32)
Record ID250122581
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.75.192/32 FUSION TELECOM PEERINGDB ASSIGNED ● high
187.16.218.176/32 FUSION TELECOM PEERINGDB ASSIGNED ● high
190.89.72.0/23 FUSION TELECOM BGP ANNOUNCED ● high
190.89.72.0/24 FUSION TELECOM BGP ANNOUNCED ● high
190.89.72.0/22 FUSION TELECOM BGP ANNOUNCED ● high
190.89.73.0/24 FUSION TELECOM BGP ANNOUNCED ● high
190.89.74.0/24 FUSION TELECOM BGP ANNOUNCED ● high
190.89.74.0/23 FUSION TELECOM BGP ANNOUNCED ● high
190.89.75.0/24 FUSION TELECOM BGP ANNOUNCED ● high
2001:12f8::218:176/128 FUSION TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::147:192/128 FUSION TELECOM PEERINGDB ASSIGNED ● high
2804:6ac8::/32 FUSION TELECOM BGP ANNOUNCED ● high
2804:6ac8:cafe::/48 FUSION TELECOM BGP ANNOUNCED ● high

IPv6 ranges (4)

CIDR
2804:6ac8::/32
2804:6ac8:cafe::/48
2001:12f8:0:9::147:192/128
2001:12f8::218:176/128

Footprint over time

9 weekly snapshots · JSON
16 +2 netblocks since 2026-07-05
2026-07-05 peak 16 2026-10-18

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (16 of 16)
No discrepancies found among checked blocks.

NIC Handles

24084183000139 ADLOL37 AS270358 AS270358 RJLSA3 RJLSA3