Barco

BGP inherited
Cluster stats
Netblocks6
Registered in Belgium (2) · Poland (2) · Australia (1) · Czechia (1)
All fragments 31 blocks across 9 clusters
Cluster ID208893031
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
59.154.179.0/29 BARCO APNIC ASSIGNED NON-PORTABLE ● low
78.10.115.32/29 Barco RIPE ASSIGNED PA ● low
78.11.84.236/30 Barco RIPE ASSIGNED PA ● low
194.7.240.0/27 BARCO-NET RIPE ASSIGNED PA ● low
195.47.28.84/30 BARCO RIPE ASSIGNED PA ● low
212.224.142.176/28 Barco RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Barco” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS2822-MNT AS6721-MNT DUMY-RIPE DUMY-RIPE MAINT-OPTUSCOM-AP MOBISTAR-MTNER NETIA-MNT OA3-AP OA3-AP