Kite API call takes more time than usual from AWS

krtrader
Hi @Vivek

the latency issue from AWS server (mumbai) to kite api call started again from tomorrow. could you please check with AWS team? I have sent you tracert logs in inbox
  • enliyo
    Noticed this as well. Especially during first half hour after market open. Many of my calls were failed on UI side which had timeout of 3 seconds for each request. So API calls /positions and /holdings were taking more than 3 seconds to complete. Why are we having connectivity issues lately?
  • sujith
    We will again raise a ticket and ask them updates regarding this.
  • krtrader
    krtrader edited May 2019
    Hi @sujith @Vivek

    The issue started again from 06-May-2019
    Can we get permanent fix for this issue from AWS? Could you please inform to them?
  • krtrader
    please look into this
  • krtrader
    Hi @sujith @Vivek

    can we get solution for this? i am facing this since 3 weeks. it increases overall slippage
  • vishnus
    Hi @krtrader we've raised this with AWS again. Since you are also in AWS network, suggest you also raise a ticket with them comparing the ping time and traceroute to api.kite.trade from your local and from your AWS instance. What is the instance type you are using?
  • krtrader
    I am using EC2 Amazon Linux ami
  • krtrader
    Hi @vishnus

    I raised ticket with AWS team last week, but not reply yet.
    Did u get any response from AWS? i am still facing the issue
  • krtrader
    Hi @sujith @vishnus

    The API calls started taking around 500 ms again from 12th Feb 2020.
    earlier it was taking <100 ms.

    Seems same issue as before. Could you please check with AWS team? I am running my app in AWS Mumbai.

    @HowUTrade are you facing similar issue?
  • sujith
    @krtrader,
    Can you do traceroute and private message the logs?
  • krtrader
    sent you message with logs
  • sujith
    There seems to be packet loss at the AWS, we have reported them to take a look at this. We are waiting for their reply.
  • krtrader
    @sujith

    The issue got resolved. Thanks for the support.
Sign In or Register to comment.