APCO

BGP inherited
Cluster stats
Netblocks7
Registered in Italy (5) · Switzerland (1) · MT (1)
All fragments 19 blocks across 10 clusters
Cluster ID209401419
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.4.55.248/30 APCO RIPE ASSIGNED PA ● low
78.4.56.224/29 APCO RIPE ASSIGNED PA ● low
78.4.107.168/30 APCO RIPE ASSIGNED PA ● low
78.4.144.200/30 APCO RIPE ASSIGNED PA ● low
78.6.45.192/30 APCO RIPE ASSIGNED PA ● low
78.133.121.96/29 apco RIPE ASSIGNED PA ● low
194.6.182.232/29 APCO-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “APCO” — 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.
Combined view of all 10 name-family clusters →
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

ALBACOM-MNT CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE GO-MNTNR