NL-BBNL-EPLUS

BGP inherited
Cluster stats
Netblocks7
All fragments 623 blocks across 425 clusters
Cluster ID205501504
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-13

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.3.8.135/32 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
31.3.15.16/29 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
31.3.15.24/31 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
31.3.15.26/31 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
31.3.15.28/30 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
91.189.210.128/28 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low
94.142.209.96/29 NL-BBNL-EPLUS RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

BREEDBAND-MNT DUMY-RIPE DUMY-RIPE