BALTCOM
Handle
Cluster stats
| Netblocks | 5 · 511 IPv4 addresses |
| All fragments | 6 blocks across 2 clusters |
| Cluster ID | 210950233 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.246.227.8/32 | BALTCOM | PEERINGDB | ASSIGNED | ● high |
| 195.246.227.136/32 | BALTCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:16::2:910:1/128 | BALTCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:16::2:910:2/128 | BALTCOM | PEERINGDB | ASSIGNED | ● high |
| 159.148.194.0/23 | BALTCOM | RIPE | LEGACY | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
No discrepancies found among checked blocks.
NIC Handles
AS20910
DUMY-RIPE
DUMY-RIPE
LATNET-MNT