API Blacklist of IP Addresses

artygus · 2013-02-07T07:10:12.000Z

I can’t use OAuth on my website, looks like hosting provider ip-address[81.177.159.5] is blocked.
Here’s tracert output:

Tracing route to api.twitter.com [199.59.149.232]
over a maximum of 15 hops:

1 <1 ms <1 ms <1 ms msk-dsr1-ae1-284.rt-comm.ru [81.176.69.129]
2 1 ms <1 ms <1 ms msk-bgw1-xe-1-3-0-0.rt-comm.ru [217.106.0.14]
3 <1 ms <1 ms <1 ms rostelecom.c.rt-comm.ru [195.161.4.138]
4 43 ms 43 ms 43 ms xe-0-0-2.frkt-ar3.intl.ip.rostelecom.ru [87.226.133.3]
5 43 ms 44 ms 44 ms ge-1-0-3.r02.frnkge04.de.bb.gin.ntt.net [213.198.82.165]
6 44 ms 44 ms 43 ms ae-4.r21.frnkge03.de.bb.gin.ntt.net [129.250.4.53]
7 58 ms 55 ms 61 ms ae-3.r22.londen03.uk.bb.gin.ntt.net [129.250.3.137]
8 56 ms 54 ms 56 ms ae-1.r02.londen03.uk.bb.gin.ntt.net [129.250.5.25]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

Trace complete.

artygus · 2013-02-07T07:10:25.000Z

issue is resolved, thanks!

episod · 2013-02-07T15:17:56.000Z

401 errors do not indicate any kind of IP blacklisting. It’s much more likely that a configuration difference (such as a wrongly set clock) is to blame.

compartetrencom · 2013-02-16T20:23:17.000Z

Hello,

I can send tweets with my computer when I use API Oauth but when I use
my web www.compartetren.com, $code = $tmhOAuth->request(‘POST’, $tmh…
i have a $code = ZERO (0)

How do know if my IP is blacklisting.

Thank you for your help and sorry for my english, i’m spanish

MelkiSch · 2013-03-18T21:25:33.000Z

I have the same problem. I’ve checked the clocks on my dev and production servers and they are well calibrated. Do you have other potential investigation routes in mind?

sufferahsmusic · 2013-04-23T05:21:22.000Z

ok i think i was black listed …i think i sent too many friend request because i was promoting my Album …i also was going from country to country and sending tweets with my link attached…i wanst aware that this was not allowed …i love being on twitter how can i fix this …

Maziyar_sh · 2013-04-24T02:31:00.000Z

I have a same problem while I’m on university campus. It works fine when I’m at home but the moment I get to the campus nothing happens. here is the result of those two commands:

curl --verbose “https://api.twitter.com/1/help/test.json”

About to connect() to api.twitter.com port 443 (#0)
Trying 199.59.148.20…
connected
Connected to api.twitter.com (199.59.148.20) port 443 (#0)
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: 2013-04-08 00:00:00 GMT
expire date: 2013-12-31 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.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
Host: api.twitter.com
Accept: /

< HTTP/1.1 200 OK
< cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< content-length: 4
< content-type: application/json; charset=utf-8
< date: Wed, 24 Apr 2013 02:29:19 GMT
< etag: “72054d9a6fbdcc7df012e19f32345b65”
< expires: Tue, 31 Mar 1981 05:00:00 GMT
< last-modified: Wed, 24 Apr 2013 02:29:19 GMT
< pragma: no-cache
< server: tfe
< set-cookie: _twitter_sess=BAh7BzoPY3JlYXRlZF9hdGwrCEmq3zk%252BAToHaWQiJTI5NjhjYWQ0NWJiMGRm%250ANGZmZWRjMzc3MzFkNDRiZGYy–0ecd674dcc33fe71eea9551ab1bf27ff69792e50; domain=.twitter.com; path=/; HttpOnly
< set-cookie: guest_id=v1%3A136677055953707034; Domain=.twitter.com; Path=/; Expires=Fri, 24-Apr-2015 02:29:19 UTC
< status: 200 OK
< strict-transport-security: max-age=631138519
< vary: Accept-Encoding
< x-frame-options: SAMEORIGIN
< x-mid: 2c858a15515be72793129705e8111c874abd6ede
< x-runtime: 0.01287
< x-transaction: dd44175942b3142f
< x-transaction-mask: a6183ffa5f8ca943ff1b53b5644ef114aba154c4
<

Connection #0 to host api.twitter.com left intact
"ok"* Closing connection #0
SSLv3, TLS alert, Client hello (1):

and:
traceroute api.twitter.com
traceroute: Warning: api.twitter.com has multiple addresses; using 199.59.148.20
traceroute to api.twitter.com (199.59.148.20), 64 hops max, 52 byte packets
1 * * *
2 202.184.111.70 (202.184.111.70) 55.344 ms 4.149 ms 67.423 ms
3 202.184.111.65 (202.184.111.65) 2.794 ms 2.028 ms 2.160 ms
4 161.142.5.249 (161.142.5.249) 5.054 ms 11.720 ms 4.522 ms
5 te0-1-0-0.bkj96.jaring.my (61.6.51.13) 4.503 ms 5.692 ms 4.282 ms
6 te0-0-1-0.bkj97.jaring.my (61.6.10.10) 6.118 ms 6.328 ms 8.313 ms
7 103.23.192.5 (103.23.192.5) 41.553 ms 39.582 ms 40.473 ms
8 xe-4-0-0-xcr1.sng.cw.net (195.2.10.178) 123.662 ms 72.833 ms 97.916 ms
9 13414.sgw.equinix.com (202.79.197.113) 71.229 ms 69.744 ms 70.522 ms
10 13414.sgw.equinix.com (202.79.197.113) 74.643 ms
xe-0-3-0.sjc2-cr2.twttr.com (199.16.159.23) 225.292 ms 260.731 ms
11 ae53.smf1-er2.twttr.com (199.16.159.41) 226.053 ms 227.757 ms 230.290 ms
12 r-199-59-148-20.twttr.com (199.59.148.20) 228.508 ms
ae53.smf1-er2.twttr.com (199.16.159.41) 232.946 ms 227.753 ms

It’s a same machine btw. If the IP addresses on-campus were blocked, any chance to bring them back?

Alidnet · 2013-05-10T10:40:36.000Z

I’m having the same issue however I went to one of our other offices and it works fine there, how do you go about getting the IP removed as i cant find any info on doing so anywhere.

Sarasvati10 · 2013-05-30T07:10:21.000Z

it’s unclear to me - I’m experiencing the same problem - if twitter blocks the server’s IP or a specific website’s IP. I have contacted the support and was lucky once, when they replied very quickly telling me that my website’s IP isn’t blocked. However the server can’t ping the api. If there were some sort of list of blocked IPs we could check withtout having to contact the support every now and then (I am sure they have better stuff to do…)

Medemblikactuee · 2013-06-12T07:01:53.000Z

No twitter updates anymore.

After making a newsitem on the website there is no twitter update anymore on twitter… Also the tweetblender plugin says

Geen tweets gevonden op #medemblik #hoorn #enkhuizen #grootebroek #hoogkarspel #andijk #lutjebroek #hem #venhuizen #wognum #opmeer #wervershoof #westwoud #wijdenes #hoogwoud #hensbroek

no tweets found …

is there a problem?

Sarasvati10 · 2013-06-12T12:56:23.000Z

well for what concerns my specific case, even though the folks of the API support had told me that my IP isn’t blocked, there seems to be a massive blacklisting of my server’s IPs. And when I say IPs I mean all of them. This is a rather peculiar situation…With all the junk I see tweeted automatically around, my sever had to be blacklisted lol
You’re probably blacklisted as well. Check with your host. If the server is “yours”, try to ping the api from the server. If not, ask you host to do that. If you have no response, then you’re probably blocked.

OctopuSocial · 2013-07-02T06:32:20.000Z

Hi how can i know if my IP have been blacklisted? my app complies with all the rules and it was doing good until today, this are the outputs:

Our server is at: 70.39.148.199

curl --verbose “https://api.twitter.com/1.1/help/test.json”

About to connect() to api.twitter.com port 443 (#0)
Trying 199.59.150.9… Connection timed out
Trying 199.59.149.232… Connection timed out
Trying 199.59.148.87… Connection timed out
couldn’t connect to host
Closing connection #0
curl: (7) couldn’t connect to host

*****@autotuits.com [~/www/tests]# traceroute twitter.com
traceroute to twitter.com (199.16.156.6), 30 hops max, 40 byte packets
1 ecvp72.inmotionhosting.com (70.39.145.127) 0.119 ms 0.081 ms 0.059 ms
2 xe-4-1-1.edge2.Washington1.Level3.net (4.79.22.109) 0.778 ms 0.809 ms *
3 * * *
4 * * *
5 * * *
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 * * *
*****@autotuits.com [~/www/tests]#

thanks

RecruitersMap · 2013-12-17T02:05:32.000Z

Is support still available for this question? I’m having the same problem connecting. Any help would be appreciated.

Sarasvati10 · 2013-12-17T08:55:00.000Z

I wouldn’t call it support. You can use the forms in support.twitter.com/forms but they’ll send an automatic reply and close the ticket. The only support you get here is from other developers with the same issue, if they bother. I changed server and resolved the problem. Other solutions aren’t known - they simply do not reply. I hope this helps.

TTechITSolution · 2014-02-22T17:06:28.000Z

212.1.214.45 , 212.1.214.76 can i get these two IPs unblacklisted… as i have taken over a vps these two are now deddicated ips. And im using them for hosting so need them unblacklisted asap please.

have tried 3 other places asking the same question.

Sarasvati10 · 2014-02-22T22:24:02.000Z

I don’t think they “unblacklist”. You’ll have ti change hosting. I ended up migrating.

hashtag_jobs · 2014-07-05T14:39:21.000Z

Hi @artygus

I know this was a while ago but how did you resolve please?

R_MUSH_INNOCENT · 2014-07-17T08:39:19.000Z

profile banner please

Neoxah · 2014-07-17T22:34:57.000Z

I’ve actually been doing extensive research on the blacklisted and what I found was very surprising. take a look. http://www.surbl.org/

andypiper · 2017-09-19T22:54:41.778Z