X6CNET
Cluster stats
| Netblocks | 18 |
| Cluster ID | 193384176 |
| 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
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-06
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 149.112.50.78/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 149.112.60.14/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 149.112.75.44/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 149.112.132.33/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 206.51.7.250/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 206.81.81.127/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 206.83.12.91/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 206.83.136.61/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 206.108.255.235/32 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::b68d/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::250/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:27::b68d:0:1/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:98::91/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:9e::61/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::78/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e2::14/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2001:505:143::4:6733:1/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
| 2602:fa3d:f4:1::44/128 | X6CNET | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(6 of 18)
No discrepancies found among checked blocks.
NIC Handles
AS46733