UMCG AMBULANCEZORG BV

UMCG_AMBULANCEZORG_BV
Data as of 2026-08-16
Registry
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2001:41f0:32a::/48)
Cluster ID223905310
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.85.191.252/30 UMCG_AMBULANCEZORG RIPE ASSIGNED PA ● low
213.125.200.52/30 UMCG_AMBULANCEZORG_BV RIPE ASSIGNED PA ● low
213.125.200.136/30 UMCG_AMBULANCEZORG_BV RIPE ASSIGNED PA ● low
2001:41f0:32a::/48 UMCG_AMBULANCEZORG RIPE ASSIGNED ● low
2001:41f0:a9d::/48 UMCG_AMBULANCEZORG_BV RIPE ASSIGNED ● low
2001:41f0:824a::/48 UMCG_AMBULANCEZORG_BV RIPE ASSIGNED ● low

IPv6 ranges (3)

Network trust

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

These blocks are registered to UMCG AMBULANCEZORG BV 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:32a::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.
2001:41f0:824a::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.
2001:41f0:a9d::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.

NIC Handles

DUMY-RIPE DUMY-RIPE ZIGGO-AUTOREG1