Yxom Network
Data as of 2026-10-04
BGP inherited
This organisation
| Netblocks | 18 |
| IPv6 | 16 prefixes (largest 2a06:9f81:4600::/44) |
| Registered in | United Kingdom (1) · Taiwan (1) |
| Record ID | 246760888 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 9 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.158.187.194/32 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 185.0.24.178/32 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:aa::178/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0::3:49ce:1/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:1::36/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::88/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::13d/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:24::24c/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:5707:ffe3::194/128 | Yxom Network | PEERINGDB | ASSIGNED | ● high |
| 2a06:9f81:4600::/44 | YXOM_NETWORK-Taipei | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4610::/44 | YXOM_NETWORK-Tokyo | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4620::/44 | YXOM_NETWORK-Frankfurt | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4630::/44 | YXOM_NETWORK-Wolverhampton | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4640::/44 | YXOM_NETWORK-Las_Vegas | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4650::/44 | YXOM_NETWORK-Amsterdam | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4660::/44 | YXOM_NETWORK-Hong_Kong | RIPE | ASSIGNED | ● low |
| 2a06:9f81:4680::/44 | YXOM_NETWORK-Seoul | RIPE | ASSIGNED | ● low |
| 2a14:67c2:700::/44 | YXOM_NETWORK-Wolverhampton | RIPE | ASSIGNED | ● low |
IPv6 ranges (16)
Footprint over time
10 weekly snapshots · JSON
18
+2 netblocks since 2026-07-26
2026-07-26
peak 18
2026-10-04
Network trust
what's this?
RPKI hygiene: C
how networks compare →
61.1%
of checked blocks have valid RPKI ROA coverage
(11 of 18)
Possible discrepancies (8)
These blocks are registered to Yxom 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:9f81:4610::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4620::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4630::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4600::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4640::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4650::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4660::/44 /44 | authorized for AS215502 — Xing Qingyu |
| 2a06:9f81:4680::/44 /44 | authorized for AS215502 — Xing Qingyu |
NIC Handles
AS215502
DUMY-RIPE
DUMY-RIPE
YXOM-MNT