KARIO-SAT
Data as of 2026-07-26
Handle
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| IPv6 | 1 prefix (largest 2001:7f8:5b::72/128) |
| Cluster ID | 214593717 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.216.40.72/32 | KARIO-SAT | PEERINGDB | ASSIGNED | ● high |
| 195.149.233.214/32 | KARIO-SAT | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:5b::72/128 | KARIO-SAT | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:7f8:5b::72/128 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
No discrepancies found among checked blocks.
NIC Handles
AS206957