The problems only affect read-write access (POST) to the Twitter API.
Read-only access (GET) is working perfectly.
It seems that Twitter has simply blocked the outbound IPs of the clusters.
A solution is currently being deployed on cluster005 and cluster007.
Comment by OVH - Tuesday, 11 March 2014, 14:34PM
+ cluster011/012/013/015
Comment by OVH - Tuesday, 11 March 2014, 15:41PM
+ cluster003/005/010/014
Comment by OVH - Tuesday, 11 March 2014, 21:10PM
+ cluster002
Comment by OVH - Thursday, 17 April 2014, 12:23PM
The problem is back again.
We are contacting Twitter about it.
RSS for all categories
The problems only affect read-write access (POST) to the Twitter API.
Read-only access (GET) is working perfectly.
It seems that Twitter has simply blocked the outbound IPs of the clusters.
A solution is currently being deployed on cluster005 and cluster007.
+ cluster011/012/013/015
+ cluster003/005/010/014
+ cluster002
The problem is back again.
We are contacting Twitter about it.