NO-BKKB-HordaLan-Dataparty

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8 · 1,288 IPv4 addresses
IPv6 4 prefixes (largest 2a00:14d8:4475::/48)
All fragments 8,116 blocks across 2,748 clusters
Cluster ID213752059
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.2.148/30 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED PA ● low
82.134.44.216/30 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED PA ● low
82.134.84.0/22 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED PA ● low
82.134.88.0/24 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED PA ● low
2a00:14d8:1001:5cb::/64 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED ● low
2a00:14d8:1001:ab7::/64 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED ● low
2a00:14d8:4475::/48 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED ● low
2a00:14d8:4aad::/48 NO-BKKB-HordaLan-Dataparty RIPE ASSIGNED ● low

IPv6 ranges (4)

Network trust

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

These blocks are registered to NO-BKKB-HordaLan-Dataparty 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:4aad::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4475::/48 /48 authorized for AS8542 — Eviny Fiber AS
82.134.84.0/22 /22 authorized for AS8542 — Eviny Fiber AS
82.134.88.0/24 /24 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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