Gemeente Voerendaal

Data as of 2026-07-26
GLEIF verified
LEI
724500Q7WAK7H6T46N72
Registered name
Gemeente Voerendaal
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2a07:3500:19d8::/46)
Cluster ID213509359
RegistryRIPE
Owner jurisdictionNL
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 724500Q7WAK7H6T46N72
Shared handles clustered on 7 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

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.21.217.144/28 Gemeente Voerendaal RIPE ASSIGNED PA ● low
178.21.222.80/28 Gemeente Voerendaal RIPE ASSIGNED PA ● low
195.35.213.28/30 GEMEENTE_VOERENDAAL RIPE ASSIGNED PA ● low
2a07:3500:19d8::/46 Gemeente Voerendaal RIPE ALLOCATED-BY-LIR ● low
2a07:3500:19d8::/48 Gemeente Voerendaal RIPE ASSIGNED ● low
2a07:3500:19d9::/48 Gemeente Voerendaal RIPE ASSIGNED ● low

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (2)

These blocks are registered to Gemeente Voerendaal 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.

2a07:3500:19d8::/48 /48 authorized for AS38915 — Solido Gemeenschappelijk Regeling
2a07:3500:19d9::/48 /48 authorized for AS38915 — Solido Gemeenschappelijk Regeling

NIC Handles

CASTEL-MNT DUMY-RIPE DUMY-RIPE LOGIUS ORG-GV81-RIPE SOLIDO-MNT ZIGGO-AUTOREG1