Erasmus MC
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 6 blocks across 3 clusters |
| Cluster ID | 208124931 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 156.83.0.0/16 | Erasmus MC | RIPE | LEGACY | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
Possible discrepancies (1)
These blocks are registered to Erasmus MC 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.
| 156.83.0.0/16 /16 | authorized for AS1103 — SURF B.V. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ORG-EMC2-RIPE
RIPE-NCC-LEGACY-MNT
SN-LIR-MNT
SURF-AUTO-MNT