BIT BV

NL-BIT6-TUNNELS

BGP inherited

Cluster stats

Netblocks	1
All fragments	142 blocks across 141 clusters
Cluster ID	206008091
Registry	RIPE
Customers	find 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

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2001:7b8:2fe::/48	NL-BIT6-TUNNELS	RIPE	ALLOCATED-BY-LIR	● high

Possibly related to this organisation

what's this?

Same name family

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

Bit6 Cust22671 Colo 1 via BIT BV sub-allocation
Bit6 Jeffz Colo 1 via BIT BV sub-allocation
Bit6 Sellv via BIT BV sub-allocation
Bit6 Ispbo Colo 1 via BIT BV sub-allocation
Bit6 Dehoa Colo 1 via BIT BV sub-allocation
Bit6 Entri Colo 1 via BIT BV sub-allocation
Bit6 Edath via BIT BV sub-allocation
Bit6 Routi Net 1 via BIT BV sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

RPKI-inferred operator BIT BV

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

BIT-MNT DUMY-RIPE DUMY-RIPE