Suisei Network
Cluster stats
Netblocks12
Cluster ID191731280
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
162.4.79.28/32 Suisei Network PEERINGDB ASSIGNED ● high
163.220.192.58/32 Suisei Network PEERINGDB ASSIGNED ● high
202.226.3.28/32 Suisei Network PEERINGDB ASSIGNED ● high
2001:de8:2000::4:9867:1/128 Suisei Network PEERINGDB ASSIGNED ● high
2001:de8:2000::4:9867:2/128 Suisei Network PEERINGDB ASSIGNED ● high
2401:5e40:c600::4:9867:1/128 Suisei Network PEERINGDB ASSIGNED ● high
2402:b7c0:e000::4:9867:1/128 Suisei Network PEERINGDB ASSIGNED ● high
2402:b7c0:e000::4:9867:2/128 Suisei Network PEERINGDB ASSIGNED ● high
2a06:41:c000::/44 Suisei-Network-JPAr-1 RIPE ASSIGNED ● low
2a06:41:c010::/44 Suisei-Network-JPAr-2 RIPE ASSIGNED ● low
2a06:41:c020::/44 Suisei-Network-JPAr-3 RIPE AGGREGATED-BY-LIR ● low
2a06:41:c030::/44 Suisei-Network-JPAr-4 RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to Suisei 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.

2a06:41:c000::/44 /44 authorized for AS49867 — Shuji Ito
2a06:41:c010::/44 /44 authorized for AS49867 — Shuji Ito
2a06:41:c030::/44 /44 authorized for AS49867 — Shuji Ito
2a06:41:c020::/44 /44 authorized for AS49867 — Shuji Ito

NIC Handles

ACRO58494-RIPE AS49867 Comet-MNT DUMY-RIPE DUMY-RIPE