Keytalk B.V.

Keytalk
Data as of 2026-07-26
GLEIF verified
LEI
724500NFX9AYVS4HEP12
Registered name
Keytalk B.V.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks7
IPv6 1 prefix (largest 2a00:1188:c::/48)
Cluster ID215260762
RegistryRIPE
Owner jurisdictionNL
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 724500NFX9AYVS4HEP12
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.22.80.160/28 Keytalk RIPE ASSIGNED PA ● low
95.142.98.16/28 Keytalk RIPE ASSIGNED PA ● low
95.142.98.96/28 KEYTALK RIPE ASSIGNED PA ● low
95.142.102.144/28 KEYTALK RIPE ASSIGNED PA ● low
178.237.33.224/28 Keytalk RIPE ASSIGNED PA ● low
178.237.33.240/28 Keytalk RIPE ASSIGNED PA ● low
2a00:1188:c::/48 Keytalk RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

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

These blocks are registered to Keytalk 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:1188:c::/48 /48 authorized for AS8455 — atom86 BV

NIC Handles

ATOM86-MNT DUMY-RIPE DUMY-RIPE