My ISP IP addresses seem to be blocked


#1

Hello,

It’s been a few years I have been using Twitter APIs from our ISP with the same IP address(s). But suddenly about an hour ago I lost all my Streaming and I can’t connect to Twitter from those machines:
This takes forever and can’t connect:
curl --verbose “https://api.twitter.com/1.1/help/test.json

  • Trying 104.244.42.194…
  • connect to 104.244.42.194 port 443 failed: Connection timed out
  • Trying 104.244.42.130…
  • After 86407ms connect time, move on!
  • connect to 104.244.42.130 port 443 failed: Connection timed out
  • Trying 104.244.42.2…
  • After 43203ms connect time, move on!
  • connect to 104.244.42.2 port 443 failed: Connection timed out
  • Trying 104.244.42.66…
  • After 21185ms connect time, move on!
  • connect to 104.244.42.66 port 443 failed: Connection timed out
  • Failed to connect to api.twitter.com port 443: Connection timed out
  • Closing connection 0
    curl: (7) Failed to connect to api.twitter.com port 443: Connection timed out

Even wget -S https://twitter.com fails

I checked multiple IP address in different subnets but all owned by this ISP, it all seem to be blocked.

Is this from Twitter or from ISP? My ISP is a largest French internet provider mostly for research units.

Many thanks.

Update: I also did send an email to api@twitter.com with my IP addresses.


#2

That is not a valid API endpoint. Where did you find that documented? It’s also not likely to work to connect to any of Twitter’s API endpoints without authentication.

Unfortunately there’s no support email at that address.

Can you traceroute to Twitter’s domains? What code have you been running?


#3

Hi Andy,

Sorry I got those info from old posts. I have been using “twit” library written in Node.js for the past 2-3 years.

Another thing that might help, I can ping api.twitter.com from home (different ISP) but I can’t ping it from my servers.

Many thanks again Andy


#4

Looks like a network routing issue - hard to say where that lies.


#5

Is there anyway to confirm it’s not from Twitter (blacklist). I guess it’s hard to believe Twitter blocked the entire Subnet of the ISP but it’s good to know for sure.

Thanks again Andy


#6

You can try raising a ticket via https://support.twitter.com/forms/platform but we’re unable to help via this forum. How many connections have you been making in the past, and what were your application(s) doing?


#7

Thanks Andy, which one is usually for blacklisted IP address? Sorry it’s my first time dealing with this.


#8

I’d use the “Not listed above” category.


#9

to answer to your question (I missed it). Each application one connection and they all use Twitter Public Streaming (some tracking, some following).
Since the other Subnets from the same ISP have the same symptoms I am guessing it is not Twitter who blacklisted the IPs. I contacted the ISP to see if they have more info.
I will follow up on the support as well.