NO BKKB COMTEC AS

NO-BKKB-COMTEC-AS
Data as of 2026-08-09
Registry
Cluster stats
Netblocks9 · 268 IPv4 addresses
IPv6 5 prefixes (largest 2a00:14d8:44be::/48)
All fragments 10 blocks across 2 clusters
Cluster ID218191518
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 · report an issue

Footprint over time

7 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-08-09

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.211.0/24 NO-BKKB-COMTEC-AS RIPE ASSIGNED PA ● low
82.134.45.236/30 NO-BKKB-COMTEC-AS RIPE ASSIGNED PA ● low
82.134.79.192/30 NO-BKKB-COMTEC-AS RIPE ASSIGNED PA ● low
82.134.94.200/30 NO-BKKB-COMTEC-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:1ed::/64 NO-BKKB-COMTEC-AS RIPE ASSIGNED ● low
2a00:14d8:1001:b5f::/64 NO-BKKB-COMTEC-AS RIPE ASSIGNED ● low
2a00:14d8:44be::/48 NO-BKKB-COMTEC-AS RIPE ASSIGNED ● low
2a00:14d8:4b46::/48 NO-BKKB-COMTEC-AS RIPE ASSIGNED ● low
2a00:14d8:4b60::/48 NO-BKKB-COMTEC-AS RIPE ASSIGNED ● low

IPv6 ranges (5)

Network trust

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

These blocks are registered to NO BKKB COMTEC 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:44be::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4b46::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4b60::/48 /48 authorized for AS8542 — Eviny Fiber AS
62.97.211.0/24 /24 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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