MEDUS
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 208817820 |
| 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 217.222.190.200/29 | MEDUS | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MEDUS” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- MEDUS-LAN 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- INFOVIA-MEDUSA sub-allocation
- MEDUSAPL-NET via Netia SA sub-allocation
- MEDUSA-FILM-SPA sub-allocation
- MEDUSA-TKU-NET via Telia Finland Oyj sub-allocation
- MEDUSASTUDIONET-PL via Netia SA sub-allocation
- Medusa sub-allocation
- FEUDIDELLAMEDUSASRL sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
TIG-MNT