Nyco Cloud Network

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks10
IPv6 10 prefixes (largest 2a13:9500:184::/48)
Record ID246760566
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:aa::230/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2001:7f8:f2:e1:0:19:7817:1/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2602:f429:31::16/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2602:f613::1978:17:1/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:1::2b/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::7f/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::80/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2a0f:5707:ffe3::189/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2a0f:7803:fc60:aaaa::1978:17/128 Nyco Cloud Network PEERINGDB ASSIGNED ● high
2a13:9500:184::/48 Nyco Cloud Network RIPE ASSIGNED ● high

IPv6 ranges (10)

Footprint over time

15 weekly snapshots · JSON
10 +1 netblocks since 2026-07-05
2026-07-05 peak 10 2026-10-04

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (8 of 10)
Possible discrepancies (1)

These blocks are registered to Nyco Cloud 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:9500:184::/48 /48 authorized for AS197817 — Yunxiao Bai

NIC Handles

AS197817 DUMY-RIPE DUMY-RIPE NCNA1-RIPE ORG-NCN4-RIPE netutils-mnt