NO BKKB Funbit AS

NO-BKKB-Funbit-AS
Registry
Cluster stats
Netblocks6
All fragments 8,116 blocks across 2,748 clusters
Cluster ID210106110
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 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
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
82.134.39.96/30 NO-BKKB-Funbit-AS RIPE ASSIGNED PA ● low
85.200.225.152/30 NO-BKKB-Funbit-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:6e1::/64 NO-BKKB-Funbit-AS RIPE ASSIGNED ● low
2a00:14d8:1001:100d::/64 NO-BKKB-Funbit-AS RIPE ASSIGNED ● low
2a00:14d8:48bf::/48 NO-BKKB-Funbit-AS RIPE ASSIGNED ● low
2a00:14d8:5072::/48 NO-BKKB-Funbit-AS RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (2)

These blocks are registered to NO BKKB Funbit AS 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.

2a00:14d8:48bf::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:5072::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

BKKB-MNT DUMY-RIPE DUMY-RIPE LYSE-MNT