GRAZHDAN
BGP inherited
Cluster stats
| Netblocks | 7 |
| Cluster ID | 210659388 |
| 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
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 92.46.250.124/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.164/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.168/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.172/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.176/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.180/30 | GRAZHDAN | RIPE | ASSIGNED PA | ● low |
| 92.46.250.188/30 | GRAZHDAN | 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.
- PERMGRAZHDANPROEKT via PJSC Rostelecom sub-allocation
- Mosgrazhdanproekt via MTS PJSC sub-allocation
- Grozgrazhdanstroy-NET sub-allocation
- POL-PRIMORGRAZHDANPROJECT-NET via PJSC Rostelecom sub-allocation
- Novosibgrazhdanproekt via PJSC Rostelecom sub-allocation
- PROMGRAZHDAN-NET via JSC "RetnNet" sub-allocation
- Pravgrazhdan via JSC Kazakhtelecom sub-allocation
- Grazhdansky 111 via PJSC MegaFon sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(7 of 7)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KNIC-MNT