A 10G SFP+ link between two UniFi devices such as a UCG-Fiber and a Pro-XG-8-PoE is supposed to run rock solid, but instead the link comes up and drops again every few seconds. This link flapping almost always has a physical cause. We work through the most common culprits from most to least likely, with the fix for each one right beside it.
Cause 1: The DAC or transceiver is incompatible
By far the most common cause is a module that is not cleanly supported. Not every DAC cable and not every fiber transceiver runs equally reliably on both ends. Some third-party modules are hard-coded for a specific target OS (for example Cisco) and are recognized by UniFi but never form a stable link. Fix: Use Ubiquiti’s own DAC cables or SFP+ modules on both sides, or hardware proven to be UniFi-compatible. A passive DAC under roughly 3 meters is the most robust and power-efficient choice for short in-rack distances. For fiber, the transceivers on both ends must match the cable type (multimode to multimode, singlemode to singlemode) and use the same wavelength. A hint of a miscoded module is a foreign vendor logged on the port, or a port that reports light or signal but never reaches a stable up state. When in doubt, cross-test the same module: if it is also unstable on a different UniFi device, the fault is in the module, not the port.
Cause 2: Cable length, cable quality and dirty connectors
Passive DAC cables have a limited reach. Beyond roughly 5 to 7 meters the signal becomes marginal for passive copper; that run belongs on an active DAC or a fiber link. On fiber, dirty or scratched connectors are a classic and often overlooked cause. Even a fingerprint or dust on the end face attenuates the optical signal enough to push the link over the edge into flapping.
Fix: Clean the LC connector and socket with a proper fiber cleaning pen (click cleaner) before plugging them in. Swap suspect patch cables for a known-good short cable and stay within the reach limits of the module type in use.
Cause 3: Speed and auto-negotiation conflict
SFP+-to-RJ45 modules and intermediate speeds (2.5G) do not negotiate reliably in every combination. If negotiation settles on no common mode, the link wobbles or falls back to 1G. Fix: In the UniFi Network controller port settings, set both ends to a fixed speed (10G, full duplex) instead of auto as a test. If that brings stability, auto-negotiation was the cause. Make sure both ports carry the same fixed setting, because one end fixed and the other end on auto produces exactly the flapping you are trying to fix. On pure 10G DAC or fiber links between two UniFi devices a fixed 10G setting is usually uncritical; only mixed speeds make negotiation tricky.
Cause 4: Outdated firmware
SFP+ behavior and module support change between firmware versions. If the two devices run different or old builds, link drops can stem directly from that. Fix: Bring both devices onto the current stable firmware and the UniFi Network controller onto a compatible version. Reboot both devices afterward and watch the port.
Cause 5: Temperature and a faulty SFP+ cage
Heat is a known killer of SFP+ ports. Copper transceivers draw considerably more power and heat than a passive DAC or a multimode module. If the temperature inside the device climbs too high, signal noise rises and the link starts to flap. Fix: Keep vents clear and leave enough space in the rack, prefer power-efficient passive DACs and avoid unnecessary copper modules. If the fault only ever appears on one specific port, the SFP+ cage itself may be defective. A loosely seated module that backs out slightly with thermal expansion can also mimic temperature-dependent flapping. Push the module firmly into the cage until the latch clicks in cleanly, and check whether the fault pattern changes afterward.
Diagnosis: how to isolate the fault
Swap and measure systematically instead of guessing. Note the exact time of each link transition and look for a pattern (temperature, load, time of day). In the controller, check the port statistics for CRC or RX errors and rising error counters, and check the system log for repeated link up/down entries.
- Check port statistics for CRC/RX errors and rising counters
- Review the system log for repeated link up/down messages
- Swap the module or DAC for a known-good Ubiquiti part
- Change ports: does the same link run stable on another SFP+ port?
- Test a fixed speed instead of auto-negotiation
- Check and update the firmware on both devices
- Clean fiber connectors and match cable length to the module limit
If the fault changes when you swap the module or port, you have isolated the cause. If it persists despite a good module, a good cable and current firmware and shows up on only one port, that points to a hardware defect in the port.
Frequently asked questions
Do I absolutely have to buy Ubiquiti DACs? No, but they save you from the most common cause. UniFi-compatible third-party parts often work; for stable operation, Ubiquiti’s own DACs and modules are the safest choice.
Why does only the fiber link flap and not the DAC? Fiber is sensitive to dirt, scratches and the wrong wavelength. Clean the connectors and check that both transceivers match the fiber type.
Are CRC errors always a cable problem? Usually yes: CRC and RX errors point to a physical problem at the module, cable or port. If the counters keep rising, swap the physical part first.
Sources: Ubiquiti Community: SFP/DAC Port Flapping and Signal Loss on UniFi US-16-XG, Lawrence Systems Forums: Check for Failing SFP+ Module Unifi Switch
