Blackfoot Communications Inc

BGP inherited
Cluster stats
Netblocks6
All fragments 32 blocks across 2 clusters
Cluster ID213182120
RegistryPEERINGDB
Customersfind customers using 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

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
206.53.175.13/32 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high
206.81.80.109/32 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high
206.81.80.209/32 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high
2001:504:16::55bb/128 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high
2001:504:16::209:0:55bb/128 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high
2001:504:58::13/128 Blackfoot Communications Inc PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

NIC Handles

AS21947