Tokyo
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2a0e:fac5::/32) |
| All fragments | 74 blocks across 39 clusters |
| Cluster ID | 213908127 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2403:ad80:3c00::/38 | Tokyo | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 2a0e:fac5::/32 | Tokyo | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:fac6::/32 | Tokyo | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
Possible discrepancies (1)
These blocks are registered to Tokyo 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.
| 2403:ad80:3c00::/38 /38 | authorized for AS134835 — Starry Network Limited |
NIC Handles
AS2428-AP
DUMY-RIPE
DUMY-RIPE
MAINT-SNL-HK
SNLA4-AP
SNLA4-AP
mnt-us-v6networking1-1