NL-BBAH-GEMARNHEM

BGP inherited
Cluster stats
Netblocks8
All fragments 353 blocks across 271 clusters
Cluster ID204824130
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
94.142.209.76/30 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.209.104/30 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.210.24/29 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.212.88/30 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.212.224/30 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.213.96/29 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
94.142.215.8/29 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low
185.65.54.72/30 NL-BBAH-GEMARNHEM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NL BBAH” — 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 271 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

BREEDBAND-MNT DUMY-RIPE DUMY-RIPE