I think my IPs got blocked

[andypiper]

Hi folks - we think this should be resolved for the time being, but investigation into the root cause is ongoing.

[AleRigatuso]

Thanks. It’s working now.

[willpower232]

Sorry to “me too” but I can’t curl either http or https from one of our servers (95.131.64.172) I presume it is affected by something similar to this?

If it helps, this seems to have kicked off for us about 8pm BST last night judging by the pile of error messages I have.

Edit: I hasten to add that its not a rackspace server…

[jehiah]

Andy, I can confirm this was also fixed for us as of about 12:00 UTC (2 hrs ago).

[andypiper]

thanks - this could be related and I’ll add your IP to our investigation. As I mentioned, we have not finished root cause analysis yet so there may be some further instability while we work to understand what happened here - we really appreciate your patience.

[mulka]

https://api.twitter.com is no longer hanging from my servers in Chicago.

[rubenfonseca]

It’s working for me too, thank you

[niwaroll]

Hi guys , I am facing the same problem .I sent an email to api@twitter.com 2 days ago , there is no response yet.We used to pull and respond to tweets from SAP CRM but now its failing.

[andypiper]

There’s no email support so I would not expect you to hear back from that email address.

What precisely is failing? Are you able to hit the same endpoints using any other tools? What errors are you seeing from the Twitter API? Can you provide a code example?

[niwaroll]

If I run the same commands from another network it works perfectly.

[niwaroll]

[andypiper]

The URL https://api.twitter.com/1/help/test.json is not a valid API endpoint and will return an error that v1 is no longer active. You also need to ensure that your application is using TLS as SSLv3 and below have been disabled on Twitter endpoints.

I’m not quite sure what the screenshots are showing me, but if you’re saying that a traceroute to api.twitter.com is failing, then this seems like a network routing issue.

[niwaroll]

Hie Andy we did some tests using another server from a different location using a new IP , we managed to make it work from the new location for only a few days until it got blocked again
this is the IP I am using 41.220.24.107
we are using TLS and I don`t think its a routing issue

[niwaroll]

Hello Andy.

Any suggestions on what course of action to pursue? Do you think it’s due to the frequency of requests? Since getting the servers whitelisted feels like a lengthy process, that might not work, we are thinking of trying this again on different servers but we don’t want them to get blacklisted too since we don’t have an endless supply of servers to test with

If it’s a frequency issue, what is the time gap between requests that won’t get us blacklisted? We’ve been using a 2-minute gap. if it’s not frequency, what else could be the cause?

Thankful for any assistance you can provide…

[andypiper]

What API endpoint(s) are you hitting?

[niwaroll]

What API endpoint(s) are you hitting?

https://api.twitter.com/1.1/statuses/update.json’
https://api.twitter.com/1.1/direct_messages.json
https://api.twitter.com/1.1/direct_messages/new.json
https://api.twitter.com/1.1/statuses/mentions_timeline.json
https://api.twitter.com/1.1/users/show.json

[andypiper]

The most common cases where I’ve seen an IP actually being blacklisted is for overactive connections to the streaming API. If you had exceeded a rate-limit on any of those endpoints you’d more likely see an API error response. Not actually being able to connect seems more likely to be a networking issue - in the case of this original thread, it turned out to be a block of Rackspace addresses and others in a similar geographic location.

Do you know the location of your server and can you name the host? When you tried the “other network” was it a different host / location?

[niwaroll]

First server is in Kampala, Uganda and the second server is in Harare, Zimbabwe

[andypiper]

I cannot speak to those specific locations, but I’m sure the specific IP you mentioned is not blocked so I would suggest doing more investigation on your networks, hosting and routing.

[ilkkah]

I just started having this problem. Cannot make connections to https://twitter.com with a browser (“Links”), nor with wget:

wget -S https://twitter.com
--2017-05-04 11:32:57--  https://twitter.com/
Resolving twitter.com (twitter.com)... 104.244.42.65, 104.244.42.193
Connecting to twitter.com (twitter.com)|104.244.42.65|:443... failed: Connection timed out.
Connecting to twitter.com (twitter.com)|104.244.42.193|:443... failed: Connection timed out.
Retrying.

--2017-05-04 11:35:04--  (try: 2)  https://twitter.com/
Connecting to twitter.com (twitter.com)|104.244.42.65|:443... failed: Connection timed out.
Connecting to twitter.com (twitter.com)|104.244.42.193|:443... failed: Connection timed out.
Retrying.

The IP address in question: (contact if needed)