SERVICE-BUND-LUEBECK-NET
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 10 blocks across 4 clusters |
| Cluster ID | 206039289 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.206.195.168/29 | SERVICE-BUND-LUeBECK-NET | RIPE | ASSIGNED PA | ● low |
| 80.149.189.96/29 | SERVICE-BUND-LUEBECK-NET | RIPE | ASSIGNED PA | ● low |
| 213.217.103.56/30 | SERVICE-BUND-LUeBECK-NET | RIPE | ASSIGNED PA | ● low |
| 2003:59:37::/48 | SERVICE-BUND-LUEBECK-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to SERVICE-BUND-LUEBECK-NET 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.
| 2003:59:37::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE
KKF-NET-NOC
MEDIASCAPE-MNT