---
title: "Comment by Arnold Holm on \"US Stock Data API Compared: Futu API vs. AllTick WebSocket for Real-Time Market Feeds\" | Hashnode"
description: "The close callback prints \"preparing to reconnect\", but this snippet does not show a reconnect policy. I would test it by dropping the connection after a confir"
url: "https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a/comment/6ad225b475a41c3e839e103d"
---

[Discussion](https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a)

Comment [US Stock Data API Compared: Futu API vs. AllTick WebSocket for Real-Time Market Feeds](https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 16](https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a/comment/6ad225b475a41c3e839e103d)

The close callback prints "preparing to reconnect", but this snippet does not show a reconnect policy. I would test it by dropping the connection after a confirmed subscription: log the disconnect time, reconnect with bounded backoff, confirm the new subscription, and compare the last timestamp before the drop with the first after it. A healthy socket after recovery does not by itself prove that the missing interval was backfilled.
