NO-BKKB-AS-Sigba-Eiendom

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks4
IPv6 2 prefixes (largest 2a00:14d8:4d28::/48)
All fragments 48 blocks across 20 clusters
Cluster ID213599832
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

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.104.212/30 NO-BKKB-AS-Sigba-Eiendom RIPE ASSIGNED PA ● low
85.200.199.56/29 NO-BKKB-AS-Sigba-Eiendom RIPE ASSIGNED PA ● low
2a00:14d8:1001:836::/64 NO-BKKB-AS-Sigba-Eiendom RIPE ASSIGNED ● low
2a00:14d8:4d28::/48 NO-BKKB-AS-Sigba-Eiendom RIPE ASSIGNED ● low

IPv6 ranges (2)

Network trust

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

These blocks are registered to NO-BKKB-AS-Sigba-Eiendom 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:4d28::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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