Babiel

Registry

Cluster stats

Netblocks	6
All fragments	10 blocks across 5 clusters
Cluster ID	209521609
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

Attribution	Registry record
Shared handles	clustered on 4 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

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
194.146.118.124/32	Babiel	PEERINGDB	ASSIGNED	● high
2001:7f8:8:0:3:901:0:1/128	Babiel	PEERINGDB	ASSIGNED	● high
217.79.210.16/30	Babiel	RIPE	ASSIGNED PA	● low
217.79.210.20/30	Babiel	RIPE	ASSIGNED PA	● low
217.79.215.64/26	BABIEL	RIPE	ASSIGNED PA	● low
217.79.215.128/25	BABIEL	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Babiel” — 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.

BABIEL-NET-228 1 blocks
BABIEL-NET-229 1 blocks
BABIEL-NET-230 1 blocks
BABIEL-NET-231 1 blocks

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.

BABIEL-NET-228 via CONET Deutschland GmbH sub-allocation
BABIEL-NET-229 via CONET Deutschland GmbH sub-allocation
BABIEL-NET-230 via CONET Deutschland GmbH sub-allocation
BABIEL-NET-231 via CONET Deutschland GmbH sub-allocation

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

AS198913 DUMY-RIPE DUMY-RIPE HRW-NOC