This is an unusual behavior; this is the first time it’s been reported to the community.
Here are similar posts, which report delay in execution, but there is no delay in execution on server side. so these delays are attributable to connectivity issue between the user and upstox, similar to mine.
% traceroute api-hft.upstox.com
traceroute: Warning: api-hft.upstox.com has multiple addresses; using 3.110.241.82
traceroute to p-udapi-order-gateway--ext-ngav2-2147028156.ap-south-1.elb.amazonaws.com (3.110.241.82), 64 hops max, 40 byte packets
1 reliance.reliance (192.168.29.1) 4.458 ms 2.756 ms 3.115 ms
2 10.233.56.1 (10.233.56.1) 4.692 ms 5.300 ms 3.977 ms
3 172.31.2.14 (172.31.2.14) 4.636 ms
172.31.1.210 (172.31.1.210) 5.805 ms 6.216 ms
4 192.168.65.150 (192.168.65.150) 4.910 ms
192.168.65.154 (192.168.65.154) 4.701 ms
192.168.65.152 (192.168.65.152) 5.181 ms
5 172.26.74.6 (172.26.74.6) 5.123 ms 4.215 ms 3.876 ms
6 172.26.77.227 (172.26.77.227) 6.546 ms 5.594 ms 6.202 ms
7 192.168.65.144 (192.168.65.144) 4.754 ms
192.168.65.138 (192.168.65.138) 6.005 ms
192.168.65.142 (192.168.65.142) 5.060 ms
8 * * *
9 * * *
10 * 99.83.67.46 (99.83.67.46) 17.652 ms
99.83.67.48 (99.83.67.48) 26.558 ms
11 52.93.141.105 (52.93.141.105) 12.365 ms
52.93.19.251 (52.93.19.251) 12.911 ms
52.93.19.243 (52.93.19.243) 11.631 ms
12 52.93.19.45 (52.93.19.45) 13.377 ms
52.93.19.93 (52.93.19.93) 13.181 ms
52.93.19.111 (52.93.19.111) 33.511 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
% curl -v https://api-hft.upstox.com
* Host api-hft.upstox.com:443 was resolved.
* IPv6: 2406:da1a:8e4:5403:d13f:6458:4d3f:5764, 2406:da1a:8e4:5401:aa73:49ed:4561:1406, 2406:da1a:8e4:5400:f64c:8f79:a81:22ee
* IPv4: 3.110.241.82, 13.126.203.253, 3.109.131.61
* Trying [2406:da1a:8e4:5403:d13f:6458:4d3f:5764]:443...
* Connected to api-hft.upstox.com (2406:da1a:8e4:5403:d13f:6458:4d3f:5764) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=*.upstox.com
* start date: May 27 00:00:00 2024 GMT
* expire date: Jun 24 23:59:59 2025 GMT
* subjectAltName: host "api-hft.upstox.com" matched cert's "*.upstox.com"
* issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
* SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://api-hft.upstox.com/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: api-hft.upstox.com]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET / HTTP/2
> Host: api-hft.upstox.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 404
< server: awselb/2.0
< date: Fri, 27 Dec 2024 12:14:10 GMT
< content-type: text/plain; charset=utf-8
< content-length: 0
<
* Connection #0 to host api-hft.upstox.com left intact
I am accessing API from Bengaluru using Jio Fiber.
Regarding the ping timeout, it seems that ICMP (ping) traffic for the HFT URL is blocked.
On one earlier occasion(a few months ago), it was working for me, so it would be good idea to confirm with the team.