Kang SAS
Data as of 2026-07-26
BGP inherited
Limited data: only 2 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 | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a01:7a0:2:1f8d::/64) |
| Cluster ID | 214477785 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
5 weekly snapshots · JSON
21
0 netblocks since 2026-07-05
2026-07-05
peak 21
2026-07-19
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.8.111.0/24 | Kang SAS | BGP | ANNOUNCED | ● high |
| 2a01:7a0:2:1f8d::/64 | Kang Kang Wang | RIPE | ASSIGNED | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2a01:7a0:2:1f8d::/64 |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
No discrepancies found among checked blocks.
NIC Handles
AS34433
DUMY-RIPE
DUMY-RIPE
FGK-MNT
JAGUAR-MNT
JAGUAR-MNT
ORG-KKW9-RIPE
ORG-UA58-RIPE
RIPE-NCC-END-MNT