IP blacklisted?


#1

I suspect that my IP address may have been blacklisted. We have a web app about to go live and I’ve been testing oauth authentication relentlessly (using the popular PHP Twitter library here: https://github.com/kertz/twitteroauth)

ping api.twitter.com
PING api.twitter.com (199.59.148.20) 56(84) bytes of data.
^C
api.twitter.com ping statistics —
15 packets transmitted, 0 received, 100% packet loss, time 14000ms

traceroute api.twitter.com
traceroute to api.twitter.com (199.59.150.41), 30 hops max, 60 byte packets
1 router1-lon.linode.com (212.111.33.229) 0.584 ms 0.640 ms 0.667 ms
2 212.111.33.233 (212.111.33.233) 0.957 ms 0.935 ms 0.947 ms
3 217.20.44.194 (217.20.44.194) 0.743 ms * *
4 ge-0.linx.london03.uk.bb.gin.ntt.net (195.66.224.138) 0.940 ms 0.960 ms 0.991 ms
5 ae-1.r02.londen03.uk.bb.gin.ntt.net (129.250.5.25) 1.699 ms 2.139 ms 2.217 ms
6 artmedia-0.a00.londen03.uk.ra.gin.ntt.net (213.130.48.90) 0.913 ms 0.901 ms 0.946 ms
7 xe-0-2-1.iad1-cr1.twttr.com (199.16.159.123) 75.458 ms xe-1-2-1.iad-cr2.twttr.com (199.16.159.125) 75.538 ms xe-0-2-1.iad1-cr1.twttr.com (199.16.159.123) 75.439 ms
8 * * *
9 ae52.smf1-er1.twttr.com (199.16.159.49) 247.093 ms 243.133 ms 247.074 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Curl does come back eventually, but only after timing out on the 1st IP.

curl --verbose http://api.twitter.com/

  • About to connect() to api.twitter.com port 80 (#0)
  • Trying 199.59.150.9… Connection timed out
  • Trying 199.59.150.41… connected

GET / HTTP/1.1
User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Host: api.twitter.com
Accept: /

< HTTP/1.1 200 OK
< Date: Tue, 22 Jan 2013 02:51:41 GMT
< Status: 200 OK
< ETag: “030e9c7328dd922a454e24434635cd4d”
< Content-Type: text/html; charset=utf-8
< Content-Length: 68315
< X-Runtime: 0.07045
< Expires: Tue, 31 Mar 1981 05:00:00 GMT
< X-Frame-Options: SAMEORIGIN
< Last-Modified: Tue, 22 Jan 2013 02:51:41 GMT
< X-Transaction: 82603abe6da4e636
< X-MID: ee846452c912a3c310e01c868c44c6ee7e997363
< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< Pragma: no-cache
< Set-Cookie: k=10.36.54.117.1358823101362530; path=/; expires=Tue, 29-Jan-13 02:51:41 GMT; domain=.twitter.com
< Set-Cookie: guest_id=v1%3A135882310136559610; domain=.twitter.com; path=/; expires=Thu, 22-Jan-2015 14:51:41 GMT
< Set-Cookie: _twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCLYTK2A8AToMY3NyZl9pZCIlMmVjYTBmZTUw%250AMmE1MTAxYzNhZTgwNmZjZDhjOWM4OGE6B2lkIiU3M2IzYzhjODFiYjA2OTc0%250AMzUxNWIwNDBhZjY2MjNkZiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6%250ARmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D–f7800c79588e8a98fccc70e81210ec988c2bf466; domain=.twitter.com; path=/; HttpOnly
< Vary: Accept-Encoding
< Server: tfe…

I contacted linode where this virtual machine is hosted, and they came back with this:

“Thank you for contacting us. This appears to be an issue with Twitter itself. Many of our staff as well as community members have been seeing issues connecting to Twitter for the majority of the day, both from our datacenters and from their local machines. You may want to use MTR to check for networking issues between your Linode and Twitter’s servers; details on MTR can be found here:”


#2

Are you still experiencing trouble? There were service-wide issues yesterday that may have caused this for you: http://status.twitter.com/post/41136790651/twitter-site-issue