Hi Taylor,
I also have a blacklisted ip address.
I have been using my personal authentication only for a few days for research purpose.
I get results from Streaming API on any other ips except a particular ip.
When I tried both ‘curl’ and ‘traceroute’ commands, I got this.
-------CURL---------
$ curl --verbose “https://api.twitter.com/1/help/test.json”* About to connect() to api.twitter.com port 443 (#0)
- Trying 199.59.150.9… connected
- Connected to api.twitter.com (199.59.150.9) port 443 (#0)
- successfully set certificate verify locations:
- CAfile: none
CApath: /etc/ssl/certs
- SSLv3, TLS handshake, Client hello (1):
- SSLv3, TLS handshake, Server hello (2):
- SSLv3, TLS handshake, CERT (11):
- SSLv3, TLS handshake, Server finished (14):
- SSLv3, TLS handshake, Client key exchange (16):
- SSLv3, TLS change cipher, Client hello (1):
- SSLv3, TLS handshake, Finished (20):
- SSLv3, TLS change cipher, Client hello (1):
- SSLv3, TLS handshake, Finished (20):
- SSL connection using RC4-SHA
- Server certificate:
- subject: C=US; ST=California; L=San Francisco; O=Twitter, Inc.; OU=Twitter Security; CN=api.twitter.com
- start date: 2012-05-02 00:00:00 GMT
- expire date: 2013-05-03 23:59:59 GMT
- subjectAltName: api.twitter.com matched
- issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa ©09; CN=VeriSign Class 3 Secure Server CA - G2
- SSL certificate verify ok.
GET /1/help/test.json HTTP/1.1
User-Agent: curl/7.21.3 (x86_64-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
Host: api.twitter.com
Accept: /
< HTTP/1.1 200 OK
< Date: Wed, 26 Dec 2012 20:55:37 GMT
< Status: 200 OK
< Pragma: no-cache
< Last-Modified: Wed, 26 Dec 2012 20:55:37 GMT
< Content-Type: application/json; charset=utf-8
< X-Runtime: 0.01738
< X-Transaction: 14cdf010ea2cf19d
< X-MID: 72a82e39be5b9a06f38f300c84eaa67d62365e52
< Content-Length: 4
< X-Transaction-Mask: a6183ffa5f8ca943ff1b53b5644ef11458609571
< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< Expires: Tue, 31 Mar 1981 05:00:00 GMT
< X-Frame-Options: SAMEORIGIN
< ETag: “72054d9a6fbdcc7df012e19f32345b65”
< Set-Cookie: k=10.36.77.106.1356555337854637; path=/; expires=Wed, 02-Jan-13 20:55:37 GMT; domain=.twitter.com
< Set-Cookie: guest_id=v1%3A13565553378604345; domain=.twitter.com; path=/; expires=Sat, 27-Dec-2014 08:55:37 GMT
< Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCIXA%252F9g7ASIKZmxhc2hJQzonQWN0aW9uQ29u%250AdHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7ADoHaWQiJWI3%250ANGY5NTdiOGI5Yjk2NWY3YzhmNjRjNjA5OTdjZWEz–c864043ff8de1978cdb5fab49f33cc3bd2cb4da1; domain=.twitter.com; path=/; HttpOnly
< Vary: Accept-Encoding
< Server: tfe
<
- Connection #0 to host api.twitter.com left intact
- Closing connection #0
- SSLv3, TLS alert, Client hello (1):
“ok”
---------TraceRoute---------
$ traceroute api.twitter.com
traceroute to api.twitter.com (199.59.149.232), 30 hops max, 60 byte packets
1 128.111.26.1 (128.111.26.1) 0.578 ms 0.694 ms 0.862 ms
2 574-c-v1071.noc.ucsb.edu (128.111.4.52) 0.532 ms 0.655 ms 0.827 ms
3 r2–574-c–2.commserv.ucsb.edu (128.111.252.148) 0.645 ms 0.712 ms 0.800 ms
4 dc-lax-dc2–dc-ucsb.cenic.net (137.164.23.2) 3.104 ms 3.103 ms 3.098 ms
5 dc-lax-core1–lax-agg1-ge.cenic.net (137.164.46.105) 4.168 ms 4.166 ms 4.161 ms
6 dc-lax-isp2–lax-core1-10ge.cenic.net (137.164.47.136) 3.279 ms 3.053 ms 3.090 ms
7 xe-9-3-0.edge5.LosAngeles1.Level3.net (4.59.48.177) 3.158 ms 3.181 ms 3.171 ms
8 vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254) 14.145 ms vlan60.csw1.LosAngeles1.Level3.net (4.69.144.62) 3.517 ms vlan70.csw2.LosAngeles1.Level3.net (4.69.144.126) 6.551 ms
9 ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) 3.324 ms ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37) 3.141 ms 3.156 ms
10 ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) 8.537 ms 8.609 ms 8.594 ms
11 ae-61-61.csw1.SanJose1.Level3.net (4.69.153.2) 20.056 ms ae-91-91.csw4.SanJose1.Level3.net (4.69.153.14) 8.584 ms ae-81-81.csw3.SanJose1.Level3.net (4.69.153.10) 8.564 ms
12 ae-3-80.edge2.SanJose3.Level3.net (4.69.152.145) 8.964 ms ae-1-60.edge2.SanJose3.Level3.net (4.69.152.17) 9.090 ms ae-3-80.edge2.SanJose3.Level3.net (4.69.152.145) 8.976 ms
13 TWITTER-INC.edge2.SanJose3.Level3.net (4.53.210.50) 9.027 ms 9.046 ms 9.130 ms
14 ae53.smf1-er2.twttr.com (199.16.159.41) 14.733 ms 14.728 ms 20.020 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I also tried to issue another curl command as follows.
$ curl -i -u penguinkang:******** http://api.twitter.com/1/account/rate_limit_status.json -v* About to connect() to api.twitter.com port 80 (#0)* Trying 199.59.148.87… connected
- Connected to api.twitter.com (199.59.148.87) port 80 (#0)
- Server auth using Basic with user ‘penguinkang’
GET /1/account/rate_limit_status.json HTTP/1.1
Authorization: Basic cGVu****************************Dg=
User-Agent: curl/7.21.3 (x86_64-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
Host: api.twitter.com
Accept: /
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Wed, 26 Dec 2012 20:58:48 GMT
Date: Wed, 26 Dec 2012 20:58:48 GMT
< Status: 200 OK
Status: 200 OK
< X-MID: 3e660da252fc4e92a
X-MID: 3e660da252fc4e92a
< X-Runtime: 0.02184
X-Runtime: 0.02184
< X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
< ETag: "0c45d2522f8bae037dc352930a76a2c8"
ETag: “0c45d2522f8bae037dc352930a76a2c8”
< Content-Type: application/json; charset=utf-8
Content-Type: application/json; charset=utf-8
< Expires: Tue, 31 Mar 1981 05:00:00 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
< Last-Modified: Wed, 26 Dec 2012 20:58:48 GMT
Last-Modified: Wed, 26 Dec 2012 20:58:48 GMT
< X-Transaction: 91569
X-Transaction: 91569
< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< Content-Length: 249
Content-Length: 249
< X-Transaction-Mask: a6183ffa5f88609571
X-Transaction-Mask: a6183ffa5f88609571
< Pragma: no-cache
Pragma: no-cache
< Set-Cookie: k=10.36.114.110.1356555528421146; path=/; expires=Wed, 02-Jan-13 20:58:48 GMT; domain=.twitter.com
Set-Cookie: k=10.36.114.110.1356555528421146; path=/; expires=Wed, 02-Jan-13 20:58:48 GMT; domain=.twitter.com
< Set-Cookie: guest_id=v1%3A135655552842424902; domain=.twitter.com; path=/; expires=Sat, 27-Dec-2014 08:58:48 GMT
Set-Cookie: guest_id=v1%3A135655552842424902; domain=.twitter.com; path=/; expires=Sat, 27-Dec-2014 08:58:48 GMT
< Set-Cookie: dnt=; domain=.twitter.com; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: dnt=; domain=.twitter.com; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Set-Cookie: lang=en; path=/
Set-Cookie: lang=en; path=/
< Set-Cookie: lang=en; path=/
Set-Cookie: lang=en; path=/
< Set-Cookie: lang=en; path=/
Set-Cookie: lang=en; path=/
< Set-Cookie: twid=u%3D64969508%7CcWNRn%2F26z02C3eitbs5dKtEcI%2FM%3D; domain=.twitter.com; path=/; secure
Set-Cookie: twid=u%3D64969508%7CcWNRn%2F26z02C3eitbs5dKtEcI%2FM%3D; domain=.twitter.com; path=/; secure
< Set-Cookie: _twitter_sess=BAh7CDoPY3xhc2hJQzonQWN0aW9uQ29u%250AdHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjo5%250AZmFlNjA5MTZkZjY3N2RkNjQwYzU5MWI1c51bddd8c9e30ab612edc8; domain=.twitter.com; path=/; HttpOnly
Set-Cookie: _twitter_sess=BAh7CDohc2hJQzonQWN0aW9uQ29u%250AdHJvbGxlcjo6oSGFzaHsABjoKQHVzQiJTU5%250AZmFlNjA5MTZkZjY3N2RkNjQwYzx****************************948428cc51bddd8c9e30ab612edc8; domain=.twitter.com; path=/; HttpOnly
< Vary: Accept-Encoding
Vary: Accept-Encoding
< Server: tfe
Server: tfe
<
- Connection #0 to host api.twitter.com left intact
- Closing connection #0
{“photos”:{“reset_time”:“Thu Dec 27 20:58:48 +0000 2012”,“reset_time_in_seconds”:1356641928,“remaining_hits”:100,“daily_limit”:100},“reset_time”:“Wed Dec 26 21:58:48 +0000 2012”,“hourly_limit”:0,“reset_time_in_seconds”:1356559128,“remaining_hits”:0}
If I issue the last command on the other ips, I still get 100 of remaining_hits. If I try my script on the banned-ip address, I get 401 error.
Is there anything that I can do to remove my IP address from your blacklist?
Thanks and happy holidays!
Jay
