VAMED-REHAKLINIK-BAD-GROENENBACH-NET
Data as of 2026-08-30
BGP inherited
Cluster stats
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2003:c5:7029::/48) |
| All fragments | 6 blocks across 2 clusters |
| Cluster ID | 233114146 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.129.213.96/29 | VAMED-REHAKLINIK-BAD-GROENENBACH-NET | RIPE | ASSIGNED PA | ● low |
| 87.190.60.240/29 | VAMED-REHAKLINIK-BAD-GROENENBACH-NET | RIPE | ASSIGNED PA | ● low |
| 2003:c5:7029::/48 | VAMED-REHAKLINIK-BAD-GROENENBACH-NET | RIPE | ASSIGNED | ● low |
| 2003:ea:11::/48 | VAMED-REHAKLINIK-BAD-GROENENBACH-NET | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE