尤伯杯API随机超时

Question

由于几个月我们面临的尤伯杯估计API很多超时。我们使用curl发出请求，这是我的测试服务器上的详细输出打印什么，当超时

curl -v \
-H 'Authorization: Token [my token]' \
-H 'Accept-Language: fr_FR' \
-H 'Content-Type: application/json' \
'https://api.uber.com/v1.2/estimates/price? start_latitude=48.8676689&start_longitude=2.3677804&end_latitude=48.8791163&end_longitude=2.3560725'
*   Trying 104.36.195.168...

当卷曲的连接停止我尝试NC在同一时间的443端口上

nc -vz 104.36.195.157 443

没有任何反应

几秒钟同一个NC命令做出响应的成功，但卷曲呼叫仍然暂停后。

卷曲会超时和重试，它最终将在这里工作了几分钟后，卷曲输出

*   Trying 104.36.194.191...
* TCP_NODELAY set
* connect to 104.36.194.191 port 443 failed: Connection timed out
*   Trying 104.36.195.168...
* TCP_NODELAY set
* After 85223ms connect time, move on!
* connect to 104.36.195.168 port 443 failed: Connection timed out
*   Trying 104.36.195.165...
* TCP_NODELAY set
* Connected to api.uber.com (104.36.195.165) port 443 (#0)

后卷曲管理连接成功，我从API响应。

有时卷曲的电话将直接工作，并作出回应的权利API结果。

此外，当我平安api.uber.com有时不响应

$ dig api.uber.com
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> api.uber.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12152
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL:

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:

;api.uber.com.          IN  A

;; ANSWER SECTION:
api.uber.com.       60  IN  CNAME   frontends.uber.com.
frontends.uber.com. 59  IN  CNAME   frontends-dca1.uber.com.
frontends-dca1.uber.com. 8  IN  A   104.36.195.158
frontends-dca1.uber.com. 8  IN  A   104.36.194.159
frontends-dca1.uber.com. 8  IN  A   104.36.194.134
frontends-dca1.uber.com. 8  IN  A   104.36.195.165
frontends-dca1.uber.com. 8  IN  A   104.36.195.162

;; Query time: 44 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Jan 17 12:33:30 CET 2019
;; MSG SIZE  rcvd: 174

$ ping 104.36.195.158
PING 104.36.195.158 (104.36.195.158) 56(84) bytes of data.
^C
--- 104.36.195.158 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2047ms

$ ping 104.36.194.159
PING 104.36.194.159 (104.36.194.159) 56(84) bytes of data.
64 bytes from 104.36.194.159: icmp_seq=1 ttl=48 time=86.0 ms
64 bytes from 104.36.194.159: icmp_seq=2 ttl=48 time=85.6 ms
64 bytes from 104.36.194.159: icmp_seq=3 ttl=48 time=85.6 ms
^C
--- 104.36.194.159 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 85.639/85.772/86.031/0.183 ms

我的测试服务器是AWS EC2 Ubuntu的18。我试图复制我的本地环境（薄荷18.3西尔维亚的Ubuntu 16.04）的问题，但它始终工作！

当测试服务器是在Ubuntu 16.04，我们似乎没有任何有问题。有没有对我目前的测试环境中的问题？

有没有人遇到相同的行为？

谢谢你的时间！

Answer 1

前几天的问题解决了没有本身在我身边的任何行动。