Posts made by trader_noob

Not able to connect to the angel one websockets. Kindly check.

Since 06 January 2025 (Monday), I have been observing wrong exchange timestamps in the market data for Futures and Options. Here is an exact example of the issue:

 seq    exch_time   ltp ltq   ttq   tbq  buy_p sell_p   tsq

1 3624059 09:33:04.000 261.8 75 15525 17825 260.85 261.80 13975
2 3624061 09:33:04.054 261.8 75 15525 17825 260.85 261.80 13975
3 3624065 09:33:04.000 261.8 75 15525 17825 260.85 261.80 13975
4 3624777 09:33:04.252 261.8 75 15525 17825 260.85 261.80 13975

As you can see there are repeated ticks of exchange time 09:33:04. Exchange times seem to be out of order. It seems that repeated ticks are being sent with non zero millisecond part. It seems to be a bug that has been recently introduced. This will obviously also cause unnecessary bandwidth costs on your end too. So I request you to resolve this ASAP.

@trader_noob @Moderator_3 @Moderator_2 @Moderator_1

Today, there are missing tokens in scrip file for NIFTY OPTIDX like NIFTY26DEC2424450CE. Kindly check ASAP.

Also, the endpoint for downloading this scrip master file is unusually slow.

@trader_noob @Moderator_1 @Moderator_2 @Moderator_3

@trader_noob @admin

@trader_noob Resolved now

Kindly rectify the issue, the websocket is suddenly disconnected.

1. Will the old endpoints ever be removed? If yes, when? (Estimated if not fixed)
2. Are there any benefits in using the new url?

@Moderator_1 Thanks for the response. MCX is still not working though.

@Mastermind Nope, seems like API servers are still not restarted

Your websockets are not relaying data for NSE scrips since 11:20 AM (19 July 2024). Resolve this ASAP. This is ridiculous!

I am connected to the websocket for data, but I have observed a weird issue that has started today only:
Every 25 seconds or so, the websocket gets stuck and takes some delay to release the incoming data. Basically, the latency (local_time - exchange_time) suddenly spikes every 25 seconds.

This has to be some server issue at your end, please check this and sort. As I said, this has started happening from today only.

@Moderator_2 Okay, seems like the issue is situational. The issue at my end occurs specifically in the opening 15 minutes. After that, throughout the day there are no issues. Seems like a server load issue if its only occuring in the opening 15 minutes, right? (The data stops coming and/or latency is too high)

@Moderator_2 A51767992

Hi

I am subscribing to 900 tokens from one websocket. The performance is very laggy. The data latency goes to more than 120 seconds some times. The data altogether stops coming which gets corrected on reconnecting. Please give us a limit on the websocket that your servers are able to handle.

I have observed that the latency for ltp data on websockets is very low (and not variable): about only 20 milliseconds - basically the network delay.

But the latency for L2 data (market depth) is very variable and high too (Anywhere from 100 ms to 2 seconds and even more!). This points that the exchange L2 data is being processed (maybe parsed or other checks, and then sent).

Can a websocket endpoint be added through which the exchange data packet is relayed as it is, so that we can parse it at our end and the data received is faster too?

(If you guys are doing packet reading at your end, the data packet can be broadcasted first (as it is) and then read at your end)

This is a feature request that I really look forward to, I request you to add this if possible!

@Sanky said in Not able to connect to the websocket, please help!:

ng issue do we need to do any updates etc

It's working at my end, no change.

@Moderator_2 thanks, its working now. Would request you to implement measures so that this issue doesn't recur.

@Moderator_2 Thanks for replying. Client Code: A51767992