Timeout - api.twitter.com

dns

#1

I am getting TIMEOUT from all my requests since I’ve changed my server. Can anyone help me to know what’s happening?

$ telnet api.twitter.com 443
Trying 199.16.156.231…
Trying 199.16.156.40…
Trying 199.16.156.8…
Trying 199.16.156.104…
telnet: Unable to connect to remote host: Connection timed out

$ traceroute twitter.com
traceroute to twitter.com (199.16.156.6), 30 hops max, 60 byte packets
1 10.1.4.41 (10.1.4.41) 0.040 ms 0.013 ms 0.012 ms
2 208.69.231.9 (208.69.231.9) 3.159 ms 3.143 ms 3.127 ms
3 74.112.175.16 (74.112.175.16) 6.933 ms 6.970 ms 6.985 ms
4 74.112.174.194 (74.112.174.194) 7.025 ms 7.065 ms 7.097 ms
5 74.112.175.0 (74.112.175.0) 7.158 ms 7.246 ms 7.316 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

$ curl -v curl --sslv3 https://twitter.com

  • Rebuilt URL to: curl/
  • Hostname was NOT found in DNS cache
  • Could not resolve host: curl
  • Closing connection 0
    curl: (6) Could not resolve host: curl
  • Rebuilt URL to: https://twitter.com/
  • Hostname was NOT found in DNS cache
  • Trying 199.16.156.102…

#2

Difficult to say, this looks like a network resolution issue.

Did you try
nslookup api.twitter.com

Has anything changed about your DNS setup?


#3

Tks for your help. Follows the result:

nslookup api.twitter.com

Server: 31.220.19.53
Address: 31.220.19.53#53

Non-authoritative answer:
Name: api.twitter.com
Address: 199.16.156.8
Name: api.twitter.com
Address: 199.16.156.199
Name: api.twitter.com
Address: 199.16.156.72
Name: api.twitter.com
Address: 199.16.156.104

I`ve changed the DNS too, didnt work.

nslookup api.twitter.com

Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: api.twitter.com
Address: 199.16.156.104
Name: api.twitter.com
Address: 199.16.156.231
Name: api.twitter.com
Address: 199.16.156.8
Name: api.twitter.com
Address: 199.16.156.40

telnet api.twitter.com 443

Trying 199.16.156.72…
Trying 199.16.156.104…
Trying 199.16.156.8…
Trying 199.16.156.40…
telnet: Unable to connect to remote host: Connection timed out

dig twitter.com +trace @8.8.8.8

; <<>> DiG 9.9.5-3ubuntu0.7-Ubuntu <<>> twitter.com +trace @8.8.8.8
;; global options: +cmd
. 19239 IN NS a.root-servers.net.
. 19239 IN NS b.root-servers.net.
. 19239 IN NS c.root-servers.net.
. 19239 IN NS d.root-servers.net.
. 19239 IN NS e.root-servers.net.
. 19239 IN NS f.root-servers.net.
. 19239 IN NS g.root-servers.net.
. 19239 IN NS h.root-servers.net.
. 19239 IN NS i.root-servers.net.
. 19239 IN NS j.root-servers.net.
. 19239 IN NS k.root-servers.net.
. 19239 IN NS l.root-servers.net.
. 19239 IN NS m.root-servers.net.
. 19239 IN RRSIG NS 8 0 518400 20160201050000 20160122040000 54549 . Og4KWlQzfEdmU9o39Hc1r1joOlqvuI8cRP7+JbL+vWLSzjux+oyZzydY c3uICf9HZ8V0llBLV+URkaYi0tssQFlxTwQb8pv4/jQMluoRPWlfEQpX TmdvQ5uKZUVFiOBakLnHSNivmZa3FFUvJ7WSalP4ikJaByMlF9GeZ/1P Icw=
;; Received 397 bytes from 8.8.8.8#53(8.8.8.8) in 119 ms

com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com. 86400 IN RRSIG DS 8 1 86400 20160201050000 20160122040000 54549 . CK/OjzffqRm2n8bHbpxNnDD9WAUC3bOWAnkm4JlPOU3ihn+Y1eh4iER2 TUj6/+Sziw0IjnnFjlBq+E1PSi3SuaTNnYPAUHYTbDltSSbwmqvZaP00 Cn1+BeGNFyf9xBe/kJ5VyN76vvw4lc4ORoRNF9nD2SXguh/1MqFgDKSg g2I=
;; Received 735 bytes from 2001:503:c27::2:30#53(j.root-servers.net) in 218 ms

twitter.com. 172800 IN NS ns1.p34.dynect.net.
twitter.com. 172800 IN NS ns2.p34.dynect.net.
twitter.com. 172800 IN NS ns3.p34.dynect.net.
twitter.com. 172800 IN NS ns4.p34.dynect.net.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20160127055812 20160120044812 28259 com. Jtz9xkhr+PIJz7CW/zEzFMboX8WfdKEWdRDobIM39NCEyQ1dhe53bRrI zl/8qBsqSTqR4BCaspKd2RVAeXIJ6SKCeyChnd8sWRTMSU+pT/aWtbIl BKHMSuu9JFat7GBsH6RVGVXGDWRGEAOFcHc0ePsDMkKpeQ5rIS/HM4v2 sWo=
7T793LI65L1MT71L2QPHR2CVKM2LT4GA.com. 86400 IN NSEC3 1 1 0 - 7T7A96RFCSHKCG13JQ843N73J4JDPG1C NS DS RRSIG
7T793LI65L1MT71L2QPHR2CVKM2LT4GA.com. 86400 IN RRSIG NSEC3 8 2 86400 20160126054126 20160119043126 28259 com. luR/LDDjcXyfKZPexsose4mfRH8OYP+AcBvNgPsxUjRX1MoCQ1rKHjJM 32qRluhD65mBVRIJqEqiBo0DelH6zJi44K4ZLrbEDt/JOHmiPtR5yOdl iU5tMUnF7MCWF+GVHrRlny0oBwdlzvs3bKIYmRFe7jBY8jeuGQNAMqIF t3U=
;; Received 675 bytes from 192.54.112.30#53(h.gtld-servers.net) in 146 ms

twitter.com. 30 IN A 199.59.150.39
twitter.com. 30 IN A 199.59.150.7
twitter.com. 30 IN A 199.59.148.10
twitter.com. 30 IN A 199.59.148.82
twitter.com. 86400 IN NS ns4.p34.dynect.net.
twitter.com. 86400 IN NS ns3.p34.dynect.net.
twitter.com. 86400 IN NS ns1.p34.dynect.net.
twitter.com. 86400 IN NS ns2.p34.dynect.net.
;; Received 190 bytes from 204.13.251.34#53(ns4.p34.dynect.net) in 18 ms


#4

#traceroute twitter.com
traceroute to twitter.com (199.16.156.230), 30 hops max, 60 byte packets
1 10.1.4.41 (10.1.4.41) 0.050 ms 0.023 ms 0.016 ms
2 208.69.231.9 (208.69.231.9) 0.927 ms 0.986 ms 1.024 ms
3 74.112.175.16 (74.112.175.16) 6.883 ms 6.905 ms 6.924 ms
4 74.112.174.194 (74.112.174.194) 6.881 ms 6.931 ms 6.958 ms
5 74.112.175.0 (74.112.175.0) 9.094 ms 9.070 ms 9.044 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *