BFIZ
BGP inherited
Cluster stats
| Netblocks | 8 |
| Cluster ID | 209595681 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 78.5.36.152/30 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.5.38.76/30 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.5.47.96/29 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.5.78.56/29 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.5.79.32/29 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.5.122.216/30 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 78.6.30.144/29 | BFIZ | RIPE | ASSIGNED PA | ● low |
| 89.118.90.192/29 | BFIZ | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?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.
- KKGP_KLUBFIZPODGOTOVKI_SHALAKYNA via JSC Kazakhtelecom sub-allocation
- CLUBFIZPODGOTOVKI via JSC Kazakhtelecom sub-allocation
- GKKP_KLUBFIZIPODGOTOVKI_AKJARSK via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
No discrepancies found among checked blocks.
NIC Handles
ALBACOM-MNT
DUMY-RIPE
DUMY-RIPE