xTom Tokyo
Cluster stats
| Netblocks | 6 |
| All fragments | 1,078 blocks across 51 clusters |
| Cluster ID | 193388232 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 101.203.89.164/32 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
| 203.190.231.8/32 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
| 210.173.177.175/32 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:7:1:0:3:258:1/128 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:5::3258:1/128 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::2:3959:1/128 | xTom Tokyo | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS3258