Sunyz Network
Data as of 2026-11-22
BGP inherited
This organisation
| Netblocks | 26 |
| IPv6 | 18 prefixes (largest 2a0f:1cc5:800::/40) |
| Registered in | United States (5) · Taiwan (2) · United Kingdom (1) |
| Record ID | 275286885 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (26)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.158.187.175/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 149.112.98.35/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 185.0.24.236/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 203.163.223.64/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 206.51.7.173/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 206.81.82.35/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 206.83.12.107/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 206.83.136.81/32 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::2:4b11/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16:1::2:4b11/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::173/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:98::107/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:9e::81/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::aabb/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:aa::236/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1:0:15:289:1/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0::2:4b11:1/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2404:f4c0:f70e:1980::150:289/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:15:289:1/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2406:d400:1:133:203:163:223:64/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f613::1502:89:1/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:5707:ffe3::175/128 | Sunyz Network | PEERINGDB | ASSIGNED | ● high |
| 2a0c:9a40:8a70::/44 | Sunyz Network | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0f:1cc5:800::/40 | Sunyz Network | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a13:a5c5:f100::/40 | Sunyz Network | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a14:7580:e600::/40 | Sunyz Network | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (18)
Footprint over time
22 weekly snapshots · JSON
26
+3 netblocks since 2026-07-05
2026-07-05
peak 26
2026-11-22
Network trust
what's this?
RPKI hygiene: C
how networks compare →
65.4%
of checked blocks have valid RPKI ROA coverage
(17 of 26)
Possible discrepancies (4)
These blocks are registered to Sunyz Network 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.
| 2a13:a5c5:f100::/40 /40 | authorized for AS150289 — Sun Yanzheng |
| 2a14:7580:e600::/40 /40 | authorized for AS150289 — Sun Yanzheng |
| 2a0f:1cc5:800::/40 /40 | authorized for AS150289 — Sun Yanzheng |
| 2a0c:9a40:8a70::/44 /44 | authorized for AS150289 — Sun Yanzheng |
NIC Handles
AS150289
DUMY-RIPE
DUMY-RIPE
MOEDOVE-MNT
NoPKT-MNT
ORG-SEVN1-RIPE
ORG-YS67-RIPE
SUNYZ-MNT
ch-ifog-1-mnt
tohu-aiden-mnt