GREYWIND AS
GREYWIND-AS
Data as of 2026-10-18
Registry
This organisation
| Netblocks | 6 |
| IPv6 | 5 prefixes (largest 2406:840:9110::/44) |
| Also registered under this name | 9 netblocks across 2 separate records |
| Record ID | 250337305 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 5 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 (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.158.187.203/32 | GREYWIND-AS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:aa::242/128 | GREYWIND-AS | PEERINGDB | ASSIGNED | ● high |
| 2602:f429:31::2b/128 | GREYWIND-AS | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::bd/128 | GREYWIND-AS | PEERINGDB | ASSIGNED | ● high |
| 2a0f:5707:ffe3::203/128 | GREYWIND-AS | PEERINGDB | ASSIGNED | ● high |
| 2406:840:9110::/44 | NET-GREYWIND-AS | APNIC | ALLOCATED NON-PORTABLE | ● low |
IPv6 ranges (5)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
Possible discrepancies (1)
These blocks are registered to GREYWIND AS 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.
| 2406:840:9110::/44 /44 | authorized for AS218796 — Yunsheng Deng |
NIC Handles
AS218796
DY1121-AP
DY1121-AP
MAINT-GREYWIND-CN
MAINT-NBDHM-CN