10G SFP+ to SFP+ Cable, 5M(16.5ft) 24AWG, 10GBASE-CU Passive Twinax Direct Attach Copper DAC Cable for Cisco SFP-H10GB-CU5M, Ubiquiti UACC-DAC-SFP10-5M, UniFi UC-DAC-SFP+ and More | 0.5-7m Available
4.9 (46 items)
Limited Time Sale$15.59 cheaper than the new price!!
Free cash-on-delivery fees for purchases over $99
Product details
| Management number | 218135366 | Release Date | 2026/05/03 | List Price | $10.40 | Model Number | 218135366 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
- Data Rate: 10GBASE-CU, 10gb/s data transfer rate.
- SFP+ Port：SFP+ to SFP+ Direct Attach Copper Passive Twinax Cable, 5m (16.5ft).
- Wire Diameter: 24AWG, It is more stable transmission and longer service life than 26/28/30AWG copper cable.
- Wide Compatibility: Compatible for Cisco SFP-H10GB-CU5M, Ubiquiti UACC-DAC-SFP10-5M, UniFi UC-DAC-SFP+, D-Link, Meraki, Fortinet, Netgear, Supermicro, Quanta, Solarflare, PaloAlto, F5 and more.
- After Sales Service：XZSNET providing 24/7 customer service, 30-day free returns, 2-year warranty and permanent technical support.
| Gauge | 24.0 |
|---|---|
| Model | XZS-DAC10G-5M |
| Frequency | 10 GHz |
| Brand Name | XZSNET |
| Cable Type | Copper |
| Item Shape | Round |
| Model Name | 10G SFP+ DAC Cable |
| Unit Count | 1.0 Count |
| Item Weight | 5.6 ounces |
| Part Number | XZS-DAC10G-5M |
| Manufacturer | XZSNET |
| Connector Type | Sfp+ |
| Number of Pins | 10 |
| Number of Items | 1 |
| Connector Gender | SFP+ to SFP+ |
| Specification Met | UL |
| Compatible Devices | Switch |
| Data Transfer Rate | 10 Gigabits Per Second |
| Included Components | 5m SFP+ Cable x1 |
| Indoor Outdoor Usage | Indoor, Outdoor |
| Compatible Phone Models | No Compatible Phone Models |
| Connectivity Technology | SFP+ to SFP+ |
| Ethernet Cable Category | Cat 6 |
| Recommended Uses For Product | SFP+ to SFP+ |
| Other Special Features of the Product | Data Transfer |
Coaxial Cables
Windows
Correction of product information
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form