IP Blacklisted?



I’m a platform engineer at Sprout Social. As of this morning we lost the ability to talk to Twitter’s API. Can you please let us know if this IP address has been blacklisted:

root@app4 2]# tracert api.twitter.com
traceroute to api.twitter.com (, 30 hops max, 40 byte packets
1 ( 0.414 ms 0.254 ms 0.378 ms
2 ( 1.034 ms 0.904 ms 1.095 ms
3 ( 1.741 ms 1.850 ms 1.774 ms
4 corea.dfw1.rackspace.net ( 2.237 ms 2.217 ms 2.215 ms
5 edge1.dfw1.rackspace.net ( 0.506 ms 0.520 ms 0.592 ms
6 xe-10-0-1.edge2.Dallas3.Level3.net ( 1.611 ms 1.551 ms 1.513 ms
7 vlan90.csw4.Dallas1.Level3.net ( 3.783 ms 3.784 ms 3.766 ms
8 ae-93-93.ebr3.Dallas1.Level3.net ( 1.871 ms 1.895 ms 1.901 ms
9 ae-7-7.ebr3.Atlanta2.Level3.net ( 22.465 ms 22.397 ms 21.911 ms
10 ae-63-63.ebr1.Atlanta2.Level3.net ( 28.297 ms 28.295 ms 28.266 ms
11 ae-1-51.edge1.Atlanta4.Level3.net ( 21.936 ms 23.050 ms 21.931 ms
12 * * *
13 * * *
14 * * *
15 * * *

If so why and what can we do to remedy that?

Rob Madden


You should be in better shape now. Are you on Amazon AWS? Sometimes when using shared hosting, you’re connectivity can be effected by bad actors sharing the same IP address ranges as you.


Thanks we’ll check it out. We’re using Rackspace.



So to be clear, our specific IP wasn’t blacklisted? Or was that network block blacklisted for other reasons?


You were likely included in a range/block that was blacklisted for other reasons – excessive crawling. If you have any reason to suspect that your application may have been performing excessive crawling at that time though, please do follow up with me: episod@twitter.com


Do you guys have the specific reason? The IP we were using is part of Rackspace’s dedicated IP block, it’s not in a cloud block. Is it possible that we were suspended for other reasons ie hitting Twitter’s API too often? If so do you know which endpoints we were abusing?


It appears our IP address ( has been blacklisted for some reason.

Beginning Saturday morning, we began to see ‘connect timed out’ errors in our application’s log files. Running a curl to https://api.twitter.com/1.1/application/rate_limit_status.json from that IP returns a series of time outs.

Running the same curl from a different IP returns the message you’d expect to see that the REST API v1 is no longer active.

If we have been blacklisted, we would have no idea as to why. We’ve been running essentially the same way, at the same volume and hitting the same API calls as we have been for the past four years, so if we did violate some rate limiting rule, it would be quite the surprise.

In any event, the IPs which were originally whitelisted back in 2009 were:

Long and short is at this point, we are dead in the water, and have been for the past two days.
If there is anything you could do, we would very much appreciate it, as this has essentially totally killed our business.

Thanks again