Then the alert came at 2:47 AM.
For 90 seconds, both radios went dark. The mine’s network dashboard showed nothing. Her phone buzzed with the first on-call manager asking for an update. She ignored it.
She scripted a loop:
The problem wasn’t the distance. It was access. Denison East sat on a frozen ridge with no road in winter. The only way to reach it was a 6-hour snowmobile ride—at dawn. The mine’s autonomous haul trucks would lose their guidance feed in three hours. At 6 AM, production would halt. Loss: $200,000 per hour.
while true; do tftp -m binary 10.0.3.88 -c put AF5X-v3.7.11.bin -t 1 sleep 11.5 done On the tenth attempt, nothing. On the twenty-third, a single acknowledgment packet came back. The East radio had bitten. But the window was only 2.7 seconds. She watched the hex dump scroll—blocks 1 through 312 of the firmware uploading at 1 Mbps over the degraded control channel. ubiquiti af-5x firmware
Marta Vasquez was the kind of engineer you called when a link was impossible. Six months ago, she’d aimed a pair of Ubiquiti AirFiber AF-5X radios across a frozen Canadian valley, through sleet and interference from a military radar station, to give the Denison Mine a 750 Mbps backbone. It had been rock-solid ever since.
She had one option: recover via the bootloader over the air. Then the alert came at 2:47 AM
At 3:54 AM, the East radio’s management IP reappeared. Then the SNR graph flickered: -65 dBm. Then -58. Then -52.
Here’s a short, engaging story about the Ubiquiti AF-5X firmware, blending real technical stakes with a touch of dramatic rescue. The 3 a.m. Pulse Her phone buzzed with the first on-call manager