Gemeente Meppel
Cluster stats
| Netblocks | 21 |
| All fragments | 1,533 blocks across 321 clusters |
| Cluster ID | 193925289 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (21)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.35.222.224/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 213.34.26.120/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 213.125.171.136/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 213.126.51.192/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 213.126.122.128/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 213.126.126.144/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 217.100.18.64/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 217.100.19.120/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 217.100.21.16/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 217.100.109.80/29 | GEMEENTE_MEPPEL | RIPE | ASSIGNED PA | ● low |
| 2001:41f0:b35::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:b4a::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:b4d::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:b52::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:b55::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:b56::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:e3e::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:606f::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2001:41f0:6b30::/48 | GEMEENTE_MEPPEL | RIPE | ASSIGNED | ● low |
| 2a07:3500:1b90::/46 | Gemeente Meppel | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a07:3500:1b90::/48 | Gemeente Meppel | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
95.2%
of checked blocks have valid RPKI ROA coverage
(20 of 21)
Possible discrepancies (10)
These blocks are registered to Gemeente Meppel 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.
| 2001:41f0:b35::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:606f::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:b4a::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:b4d::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:b52::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:b55::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:b56::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2a07:3500:1b90::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:e3e::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
| 2001:41f0:6b30::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
NIC Handles
AS6830-MNT
CASTEL-MNT
DUMY-RIPE
DUMY-RIPE
LOGIUS
ORG-GM140-RIPE
TNF-MNT
ZIGGO-AUTOREG1