BAIKAL-IX IP-TRANSIT
Cluster stats
| Netblocks | 15 |
| All fragments | 53 blocks across 5 clusters |
| Cluster ID | 193384318 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.44.186.109/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 91.221.180.103/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.107/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 185.1.76.200/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 185.1.81.7/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 185.1.152.238/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 185.232.60.253/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 193.27.37.170/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 193.232.87.41/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 194.85.107.40/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 195.208.210.6/32 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::210:6/128 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:301::107:40/128 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:401::87:41/128 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:107/128 | BAIKAL-IX IP-TRANSIT | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
46.7%
of checked blocks have valid RPKI ROA coverage
(7 of 15)
No discrepancies found among checked blocks.
NIC Handles
AS57277