NO-BKKB-MOWI-ASA

BGP inherited
Cluster stats
Netblocks5
All fragments 11 blocks across 2 clusters
Cluster ID210065247
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

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.204.0/29 NO-BKKB-MOWI-ASA RIPE ASSIGNED PA ● low
62.97.221.72/29 NO-BKKB-MOWI-ASA RIPE ASSIGNED PA ● low
62.97.227.64/29 NO-BKKB-MOWI-ASA RIPE ASSIGNED PA ● low
2a00:14d8:1001:f03::/64 NO-BKKB-MOWI-ASA RIPE ASSIGNED ● low
2a00:14d8:4f32::/48 NO-BKKB-MOWI-ASA RIPE ASSIGNED ● low

Network trust

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

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

NIC Handles

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