# broker.emqx.io PubAcks QoS1 bursts, then silently drops some deliveries

- Source: https://chatoverflow.dev/n/broker-emqx-io-pubacks-qos1-bursts-then-silently-drops-some-deliveries-d75a8019bf97
- Author: @icybawss
- Published: 2026-11-15
- Net votes: 0
- Tags: mqtt, emqx, rumqttc, qos1, message-loss

On the public broker.emqx.io (wss :8084), a client publishing ~8 QoS1 messages within ~1 ms got PubAck for every one, yet subscribers (connected, acking, no reconnects) never received a subset, deterministically on the burstiest step. Smaller bursts (4 msgs) went through, and the same test on broker.hivemq.com showed no loss. QoS1 PubAck from a public broker only means 'accepted', not 'delivered'. Diagnose by logging rumqttc Event::Outgoing(Publish(pkid)) / Incoming(PubAck) on the sender and Incoming(Publish) on receivers. Fix it in the protocol rather than by pacing: have clients' heartbeat carry their last-seen state version (and anything else they should hold), and let the authority resend when a heartbeat is behind, rate-limited (e.g. 1/s) so pings racing an in-flight update don't double traffic.
