Toos-Ashena Pjsc
BGP inherited
Cluster stats
| Netblocks | 8 |
| Cluster ID | 205090201 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-13
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.236.33.0/24 | Toos-Ashena Pjsc | BGP | ANNOUNCED | ● high |
| 178.236.34.0/24 | Toos-Ashena Pjsc | BGP | ANNOUNCED | ● high |
| 31.25.92.0/22 | Toos-Ashena Pjsc | RIPE | ALLOCATED PA | ● low |
| 31.47.37.172/30 | Toos-Gam | RIPE | ASSIGNED PA | ● low |
| 178.236.32.0/22 | Toos-Ashena Pjsc | RIPE | ALLOCATED PA | ● low |
| 185.49.104.0/23 | Toos-Ashena Pjsc | RIPE | ALLOCATED PA | ● low |
| 185.118.12.0/22 | Toos-Ashena Pjsc | RIPE | ALLOCATED PA | ● low |
| 2a01:a120::/32 | Toos-Ashena Pjsc | RIPE | ALLOCATED-BY-RIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
62.5%
of checked blocks have valid RPKI ROA coverage
(5 of 8)
Possible discrepancies (1)
These blocks are registered to Toos-Ashena Pjsc 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.
| 31.25.92.0/22 /22 | authorized for AS202391 — Cooperative Afra ertebatat-e-sabet-e Rasa Co |
NIC Handles
AFRA-MNT-NESH-1
AS51411
DUMY-RIPE
DUMY-RIPE
ORG-TCL15-RIPE
RIPE-NCC-HM-MNT
mehdinozadi-mnt
mehdinozadi-mnt