I am writing to request urgent assistance with the 20-depth market data WebSocket API (wss://depth-api-feed.dhan.co/twentydepth).
The feed was working perfectly until June 18th, but it stopped streaming data on June 19th. Please note that the connection establishes without throwing any error codes, but no data payload is being received.
My Data API subscription is active and valid until July 27th. Could you please verify if there have been recent updates or changes to the WebSocket configuration?
Additionally, we have noted a critical pattern: The API fails completely at market open, delivering no data. However, after making multiple manual reconnection retries, the stream suddenly begins functioning normally around 10:30 AM.
This behavior strongly suggests that the underlying server may be facing resource constraints or concurrency bottlenecks during peak market-open hours, preventing it from serving all client connections properly. As this is a premium, paid data subscription (currently valid until June 27th), we expect reliable infrastructure and proper resource allocation to support live trading operations.
Could you please investigate this server-side bottleneck urgently and verify if any recent configuration changes have impacted this endpoint? Since this impacts our live operations, your prompt assistance in resolving this would be highly appreciated.
+1 — confirming the same issue, and it’s not isolated to one account.
I’m seeing the exact behaviour you describe on the 20-depth feed (twentydepth, RequestCode 23): the WebSocket connects, the RequestCode 23 subscription is accepted with no error code, but then no/very little data payload arrives. THIS IS PURELY ABOUT OPTIONS MARKET DEPTH OTHERS LIKE EQUITY DEPTH AND FUTURE DEPTH ARE FINE.
Started Friday 19 June 2026, still happening Monday 22 June.. @Sammy could we get an update on the 20-depth feed status please?
This may be due to a temporary issue with the 20-depth feed during peak market hours. Since the connection is established but data starts flowing only after a few retries, there could be some delay or load-related behavior at market open.
It may be worth observing whether the same pattern continues over the next few sessions and whether it is limited to specific segments or instruments.
I noticed that users with the Community Maverick tag usually have the answers to most of these issues. However, looking at your comment, that doesn’t seem to be the case here. Please disregard.
I agree, but this temporary issue with the 20-depth feed during peak hours comes with a financial cost that we are actively paying for. Today, right in the middle of the trading session, the 20-depth market feed completely stopped responding again.
@Hardik@Bhavya_Jain@Divyesh@Jubin_Varghese@PravinJ@Vaibhav_Lad@Mohseen_Usmani@MahimaShah@Madiya_Khatri@Mrunmayi_Vaity
Can we please find an immediate solution to this issue? It is actively hampering live trading sessions and occurring on an intermittent, random basis. This needs to be treated as a top-priority fix; users are paying a premium for a critical feature that suddenly stops functioning, yet it feels like it is not getting the attention it requires. For a paid service, restoring system stability must take priority over everything else.