I think my IPs got blocked

[AleRigatuso]

Mulka, could you ask to the guys on Rackspace, to call Twitter? They will have a faster response. I’ve already filled a ticket, both on Twitter and Rackspace.

[mulka]

Just talked to a rackspace support person. They’re on it. As much as they can be anyways. I have a feeling this one is on Twitter’s end. In the meantime, I moved my app to Virginia.

[rubenfonseca]

Suffering from exactly the same problem with some servers in Chicago

[andypiper]

Hello everyone.

Thanks for the reports and apologies for the frustration this is causing. We’re looking into the issue.

Appreciate that folks may not want to share IP addresses in public but if anyone is able to share an IP in the Rackspace range that is known to be affected we can look into it more quickly.

[jehiah]

Andy, I’m not at Rackspace, but I can confirm that i’m seeing similar issues where ssl connections to api.twitter.com are dropped which causes the client to appear to hang and timeout before ssl handshake is complete. I’m connecting from 69.58.188.0/24

From my monitoring, this issue exactly 5hrs ago for me at 04:30 UTC.

[AleRigatuso]

Hi Andy,

The problem still continues. It worked for an hour, but then it stopped working again. If you give me an email I’ll send you the IP’s of our servers. We’ve also filled a ticket on twitter with the list our IPs ( Case# 06660174: general question - AleRigatuso - ref:00DA0000000K0A8.500G000000W6plz:ref ).

Thanks,
Alejandro

[andypiper]

Thanks, that ticket info will be helpful.

[andypiper]

thanks for this information, we’re studying this now.

[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.