IP blocked

zazz_com_au · 2012-10-18T22:24:34.000Z

Hi there,

We have a script which runs at midnight (Australian Eastern Time) daily which posts our latest deals. We find we can only make about 15-20 tweets before our IP is blocked. If we change IP the tweets return. This only happens once a day, so there is no way we can be exceeding the API limit.

Traceroute from our server

traceroute to twitter.com (199.59.149.230), 30 hops max, 60 byte packets
 1  111.67.5.254 (111.67.5.254)  0.272 ms  0.263 ms  0.258 ms
 2  216.14.207.89 (216.14.207.89)  0.688 ms  0.688 ms  0.681 ms
 3  ip-201.197.31.114.VOCUS.net.au (114.31.197.201)  14.935 ms  14.936 ms  14.930 ms
 4  ip-160.196.31.114.VOCUS.net.au (114.31.196.160)  171.281 ms  171.514 ms  171.509 ms
 5  ip-159.196.31.114.VOCUS.net.au (114.31.196.159)  171.262 ms  171.497 ms  171.489 ms
 6  ip-162.196.31.114.VOCUS.net.au (114.31.196.162)  171.229 ms  171.020 ms  171.009 ms
 7  ten-0-5-0-1.cor01.syd04.nsw.VOCUS.net.au (175.45.72.118)  170.988 ms  171.178 ms  171.169 ms
 8  ten-0-0-0-2.cor01.sjc01.ca.VOCUS.net (114.31.199.36)  171.164 ms  171.162 ms  171.157 ms
 9  ip-181.199.31.114.VOCUS.net.au (114.31.199.181)  171.152 ms  171.509 ms  171.506 ms
10  ip-185.199.31.114.VOCUS.net.au (114.31.199.185)  170.829 ms  170.836 ms  170.832 ms
11  eqix2.cr2.sjc2.twttr.com (206.223.116.101)  195.469 ms  195.470 ms  195.116 ms
12  xe-1-0-0.smf1-er2.twttr.com (199.16.159.41)  199.444 ms  199.726 ms  199.549 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *

Traceroute from our office:

traceroute: Warning: twitter.com has multiple addresses; using 199.59.150.7
traceroute to twitter.com (199.59.150.7), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  7.609 ms  1.410 ms  1.928 ms
 2  10.20.21.105 (10.20.21.105)  21.881 ms  20.095 ms  17.983 ms
 3  203-12-162-161.tpgi.com.au (203.12.162.161)  17.706 ms  17.680 ms  16.355 ms
 4  nme-nxg-wal-crt2-te-2-1-0.tpgi.com.au (202.7.171.89)  47.941 ms  20.819 ms  23.831 ms
 5  syd-sot-ken2-crt1-ge-0-1-0.tpgi.com.au (202.7.171.137)  27.763 ms  101.917 ms  26.634 ms
 6  ix-11-1-0-0.tcore2.tv2-tokyo.as6453.net (116.0.88.21)  127.247 ms  129.169 ms  127.185 ms
 7  180.87.181.6 (180.87.181.6)  130.476 ms  126.891 ms  128.376 ms
 8  xe-0-3-0.pao1-cr2.twttr.com (199.16.159.15)  303.359 ms  306.774 ms  307.126 ms
 9  xe-11-0-0.smf1-er2.twttr.com (199.16.159.55)  307.192 ms  405.411 ms  237.162 ms
10  r-199-59-150-7.twttr.com (199.59.150.7)  238.405 ms  340.552 ms  307.261 ms

How do we get our IP unblocked and able to post again?

episod · 2012-10-19T14:57:06.000Z

Verify you’re using the right URLs and none that have been recently retired. Make sure you listen to HTTP error codes and that you follow them. If your requests result in many error codes, you should be exponentially backing off.

It’s not clear that your IP addresses are blocked. If this happens for you like clockwork it’s much more likely you’re just not interpreting errors correctly or using the API appropriately.