BTA-Kazan
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 293 IPv4 addresses |
| Cluster ID | 209598078 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 95.167.78.96/29 | BTA-Kazan | RIPE | ASSIGNED PA | ● low |
| 95.167.103.0/24 | BTA-Kazan | RIPE | ASSIGNED PA | ● low |
| 217.30.249.192/27 | BTA-Kazan | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to BTA-Kazan 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.
| 95.167.103.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT
TIC-NOC-MNT