F6 Networks

BGP inherited
Cluster stats
Netblocks6
Cluster ID208802197
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

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
198.179.18.56/32 F6 Networks PEERINGDB ASSIGNED ● high
206.71.137.6/32 F6 Networks PEERINGDB ASSIGNED ● high
206.130.15.20/32 F6 Networks PEERINGDB ASSIGNED ● high
2001:504:2d::18:56/128 F6 Networks PEERINGDB ASSIGNED ● high
2001:504:37:10::200/128 F6 Networks PEERINGDB ASSIGNED ● high
2001:504:37:30::60/128 F6 Networks PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
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

AS3367