I’ve been using the twitter API for a while now without any problem, however in the last few days I’ve been having quite a few problem with connection to api.twitter.com timing out.
The error i’m getting is a fairly straightforward
Error: connect ETIMEDOUT 220.127.116.11:443 in node. Doing some checks, the DNS can be resolved properly and the latency is okay (I guess depending if I hit a EU or a US server)
# ping api.twitter.com PING api.twitter.com (18.104.22.168): 56 data bytes 64 bytes from 22.214.171.124: icmp_seq=0 ttl=57 time=8.336 ms 64 bytes from 126.96.36.199: icmp_seq=1 ttl=57 time=8.378 ms
# ping 188.8.131.52 PING 184.108.40.206 (220.127.116.11): 56 data bytes 64 bytes from 18.104.22.168: icmp_seq=0 ttl=53 time=96.461 ms 64 bytes from 22.214.171.124: icmp_seq=1 ttl=53 time=96.505 ms
Anyway I was wondering if anybody else is having a similar issue? This starting showing up in the last few days, it still works most of the time it’s just not very reliable. If it’s of any interest the server is running in OVH.