SDCC OpenNetwork

BGP inherited
Cluster stats
Netblocks8
Registered in Japan (3) · China (1)
Cluster ID208805650
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
163.220.192.7/32 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
163.220.192.17/32 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
202.226.3.7/32 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
2401:5e40:c600::3:8074:1/128 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
2401:5e40:c600::3:8074:2/128 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
2402:b7c0:e000::3:8074:1/128 SDCC OpenNetwork PEERINGDB ASSIGNED ● high
218.57.131.240/28 SDCC-COM APNIC ASSIGNED NON-PORTABLE ● low
2406:7ec0::/33 SDCC-IPv6 APNIC ALLOCATED NON-PORTABLE ● low

Network trust

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

These blocks are registered to SDCC OpenNetwork 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:7ec0::/33 /33 authorized for AS140868 — Ayao Takata

NIC Handles

AS2777-AP AS38074 DS95-AP DS95-AP MAINT-CNCGROUP-SD MAINT-SDCC-US SDCC1-AP SDCC1-AP