COM-IN Telekommunikation
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 20 blocks across 3 clusters |
| Cluster ID | 207727578 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.197.71/32 | COM-IN Telekommunikation | PEERINGDB | ASSIGNED | ● high |
| 185.1.208.229/32 | COM-IN Telekommunikation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::c8ca:0:1/128 | COM-IN Telekommunikation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:44::c8ca:0:1/128 | COM-IN Telekommunikation | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “COM IN” — 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.
- COM-IN Telekommunikations GmbH 15 blocks
- Com In Space Office AB 1 blocks
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
AS51402