> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metar.ws/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Recent fixes and protocol updates to the METAR.ws stream.

<Update label="24 July 2026">
  We shipped a few fixes over the past couple of days aimed squarely at connection reliability — the kind of thing that matters most if you're running a bot against the stream.

  **Duplicate deliveries fixed**

  Some reports were reaching clients twice when they arrived through two ingestion paths at once. Each observation now reaches you exactly once.

  **Stale connection slots fixed**

  A half-dead connection could silently hold onto a connection slot indefinitely, which showed up as random-looking per-station staleness on Starter plans until you reconnected from scratch. The server now detects and reaps dead connections on its own, so a slot frees up the moment a connection actually drops.

  **`report_time` accuracy fixed**

  In some cases, the reported time drifted from the actual observation time. It's now derived directly from the raw METAR body, so it always matches what you'd parse yourself.

  **Protocol addition: cached replay flag**

  When you reconnect, we replay the last known value for each channel so you're never starting from nothing; see [Heartbeats & Reconnection](/protocol/heartbeats-reconnection). Those replayed observations are now explicitly flagged with `"cached": true` in the payload.

  If your bot measures latency (time from observation to receipt), filter these out. A cached replay isn't a fresh push, and counting it as one will throw your latency numbers off. Live pushes remain unflagged, same as always.
</Update>