Gemeente Heerlen

BGP inherited
Cluster stats
Netblocks6 · 533 IPv4 addresses
Cluster ID209161130
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

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.222.16/28 Gemeente Heerlen RIPE ASSIGNED PA ● low
193.203.220.0/23 Gemeente Heerlen RIPE ASSIGNED PI ● low
213.126.70.184/29 GEMEENTE_HEERLEN RIPE ASSIGNED PA ● low
2a07:3500:1200::/46 Gemeente Heerlen RIPE ALLOCATED-BY-LIR ● low
2a07:3500:1200::/48 Gemeente Heerlen RIPE ASSIGNED ● low
2a07:3500:1201::/48 Gemeente Heerlen RIPE ASSIGNED ● low

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 (3)

These blocks are registered to Gemeente Heerlen 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:1200::/48 /48 authorized for AS38915 — Solido Gemeenschappelijk Regeling
2a07:3500:1201::/48 /48 authorized for AS38915 — Solido Gemeenschappelijk Regeling
193.203.220.0/23 /23 authorized for AS38915 — Solido Gemeenschappelijk Regeling

NIC Handles

DUMY-RIPE DUMY-RIPE LOGIUS ORG-GH106-RIPE RIPE-NCC-END-MNT SOLIDO-MNT ZIGGO-AUTOREG1