PARASAT
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 26 blocks across 4 clusters |
| Cluster ID | 205941041 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 92.46.51.236/30 | PARASAT | RIPE | ASSIGNED PA | ● low |
| 126.209.79.12/30 | PARASAT | APNIC | ALLOCATED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “PARASAT” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Parasat Cable TV, Inc 20 blocks
- PARASAT-AP 2 blocks
- PARASAT-PH 2 blocks
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.
- Kollparasat 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
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
AI782-AP
DUMY-RIPE
DUMY-RIPE
IIA37-AP
IIA37-AP
KNIC-MNT
MAINT-INFINIVAN-PH