Layer23 BV
BGP inherited
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID193383476
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.160.178/32 Layer23 BV PEERINGDB ASSIGNED ● high
185.1.223.71/32 Layer23 BV PEERINGDB ASSIGNED ● high
193.178.185.187/32 Layer23 BV PEERINGDB ASSIGNED ● high
193.239.117.216/32 Layer23 BV PEERINGDB ASSIGNED ● high
2001:7f8:13::a503:4766:2/128 Layer23 BV PEERINGDB ASSIGNED ● high
2001:7f8:19:1::87ce:1/128 Layer23 BV PEERINGDB ASSIGNED ● high
2001:7f8:b7::a503:4766:1/128 Layer23 BV PEERINGDB ASSIGNED ● high
2001:7f8:10f::87ce:178/128 Layer23 BV PEERINGDB ASSIGNED ● high
2a07:a80::/48 Layer23 RIPE ALLOCATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
77.8% of checked blocks have valid RPKI ROA coverage (7 of 9)
Possible discrepancies (1)

These blocks are registered to Layer23 BV but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a07:a80::/48 /48 authorized for AS34766 — atom86 BV

NIC Handles

AS34766 DUMY-RIPE DUMY-RIPE LAYER23-MNT