PJSC Moscow city telephone network
DZ
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 824 blocks across 780 clusters |
| Cluster ID | 206389130 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.255.24.144/29 | DZ-NET | RIPE | ASSIGNED PA | ● low |
| 80.255.24.160/28 | DZ-NET | RIPE | ASSIGNED PA | ● low |
| 210.72.235.240/29 | DZ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 219.153.6.232/30 | DZ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2a14:67c2:824::/48 | DZ | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
60.0%
of checked blocks have valid RPKI ROA coverage
(3 of 5)
No discrepancies found among checked blocks.
NIC Handles
BQ4-AP
BQ4-AP
DUMY-RIPE
DUMY-RIPE
MAINT-CHINANET-CQ
MAINT-CNNIC-AP
TASCOM-MNT-RIPE
TIANJIN-JIANRONGWANGLUO-MNT
ZL235-AP
ZL235-AP