NO-BKKB-TRIGGER

Data as of 2026-11-22
BGP inherited
This organisation
Netblocks6
IPv6 3 prefixes (largest 2a00:14d8:4568::/48)
Also registered under this name 10 netblocks across 3 separate records
Record ID275909711
RegistryRIPE
Customerssee who runs inside 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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.69.152/30 NO-BKKB-TRIGGER RIPE ASSIGNED PA ● low
82.134.94.48/30 NO-BKKB-TRIGGER RIPE ASSIGNED PA ● low
85.200.241.220/30 NO-BKKB-TRIGGER RIPE ASSIGNED PA ● low
2a00:14d8:1001:754::/64 NO-BKKB-TRIGGER RIPE ASSIGNED ● low
2a00:14d8:4568::/48 NO-BKKB-TRIGGER RIPE ASSIGNED ● low
2a00:14d8:4745::/48 NO-BKKB-TRIGGER RIPE ASSIGNED ● low

IPv6 ranges (3)

Footprint over time

19 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-11-22

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-TRIGGER 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:4568::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4745::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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