1. Home
  2. Categories
  3. General Discussion
  4. High TCP connect failure rate to apiconnect.angelone.in from registered server IP

High TCP connect failure rate to apiconnect.angelone.in from registered server IP

General Discussion
Log in to reply
  • N

    Subject: SmartAPI connectivity — high TCP connect failure rate from registered IP

    Client code: R58519218
    Registered IP: 142.93.211.114

    I am seeing a high rate of failed TCP connections to apiconnect.angelone.in from my registered server IP. Measured just now: 3 out of 10 fresh HTTPS connects succeeded; the rest timed out at 5 seconds. Login attempts (generateSession) are failing repeatedly as a result. An MTR trace shows ~49% packet loss at the destination hop.

    My hosting provider recently resolved an unrelated upstream block on this IP, and other destinations have since recovered fully, so I am trying to determine whether anything on the SmartAPI side is contributing.

    Could you please check:

    1. Is the IP 142.93.211.114 currently registered and in good standing for my API access?
    2. Is there any rate limiting, throttling, or block applied to this IP, possibly triggered by repeated failed connection attempts over the past few days?
    3. Are there any known connectivity issues affecting apiconnect.angelone.in?

    I can provide full MTR output on request.
    Angel's SmartAPI docs state the session remains active till 12 midnight unless the user logs out. Confirm our angelone_papa lazy-login model and any expiry assumptions match that documented behaviour — and check we haven't invented another "~" constant the way commit 918bca1 did for Kite. If we have an assumed Angel expiry anywhere, replace it with the documented rule and cite the source in the code comment.

    0