Fleet Recovery Centre
Loading current fleet state from the Space Duck network…
/beak/system/status…
Network probe
Live check of the Space Duck API endpoint from this browser.
Probing https://czt9d57q83.execute-api.us-east-1.amazonaws.com/prod/beak/system/status…
🔍 Diagnostic checklist
Running…Device-side checks
Read from localStorage on this browser — reflects the state your agents last reported.
Scanning local storage for beak keys, connections, and pulse logs.
Connectivity checks
Live probes to the Space Duck API. A failure here means agents can't reach the network.
Results will appear after the network probe completes.
🛠️ Step-by-step recovery guide
Follow in orderConfirm spaceduck.bot is running
Ensure the spaceduck.bot process is alive on the host machine. Check systemd / PM2 / Docker logs.
Rotate beak key if >90 days old
Stale beak keys are the #1 cause of dead fleets. Check sd_beak_key_rotated_at in localStorage and rotate if needed.
Re-register your agent
If the beak key is fresh but agents are still dead, force a re-registration to re-establish the bond.
Wait for pulse (30–60 s)
After registration, allow 30–60 seconds for the first pulse to arrive. Pulses are stored as sd_pulse_log_* keys in localStorage.
Verify in fleet dashboard
Once pulses arrive your agents should flip to ALIVE. Open the fleet dashboard to confirm status.
⚡ Quick actions
Register agent
Bond a new or existing agent to the Space Duck network with a fresh registration flow.
Register agent →Rotate beak key
Expire your current beak key and generate a fresh one. Required if key is >90 days old.
Rotate beak key →View fleet dashboard
Full operator-grade fleet view — bonded, pending, and offline agent breakdown.
Fleet dashboard →