April 27th, 2026
1.10.16 - Added logs for easier debugging on missed heartbeats or config fetches. Failed certificate issuing requests now log the reason, including "no fresh heartbeat sent", so it's clearer why a data connection can't be established. Tailscale config fix so it doesn't lose state at restarts such as client version upgrades (please report if tailscale issues continue). (Mar 27th)
1.10.17 - Show beast stats instead of JSON on the :8088 dashboard when beast is enabled. Fixed an issue where some invalid config could cause the beast port to not be open, which should make more stations eligible for beast. (Apr 1st)
1.10.18 - Added support for sending BEAST data directly to NATS, bypassing legacy infrastructure. Attempted fix for a port conflict by closing the BEAST listener explicitly on shutdown. (Apr 16th)
1.10.19 - Beast first! Stations now start up in beast mode. If readsb isn't configured for beast but JSON is functioning, the station will fall back to sending JSON after a 90s grace period. The client will continue to monitor the beast connection and, once data is flowing on the beast port (30015), it will automatically switch to Beast mode and stay there. An extra heartbeat is sent once NATS Direct Connect is connected to signal a successful connection and limit early off-line status. The Station diagnostics page also has an added connectivity test toward the NATS Direct Connect endpoint (along with BYOD wingbits status command). (Apr 16th)
1.10.20 - Attempting to fix clients connecting directly with expired tokens by NTP compensating the clock so expiry calculation is more accurate. (Apr 17th)
TGE rewards page - Now shows data from the actual beta reward tables, and the language has been updated to reflect that it is final.
Dashboard graph cache - The cache on the Overview dashboard graph is now one hour instead of resetting at midnight each day. This should help reduce some of the confusion around when the graph updates.
Heartbeat requirement tightened - In addition to the existing checks (heartbeat count, satellite count, and geolocation within the station's hex), stations must now have sent a recent heartbeat for us to accept their data and award rewards. We're starting with a requirement of at least one heartbeat in the last 2 hours. Heartbeats are crucial for our processing of beast frames and for being able to review the state of the station fleet, so this change makes it more apparent when a station isn't reporting in.
BEAST data direct to NATS (rollout) - We have started gradually rolling out the new path where BEAST data goes directly to NATS, bypassing legacy infrastructure. Station owners shouldn't really notice much. The main observable change is that data is now going to ingest.wingbits.com instead of feed.wingbits.com.