Just to say it, this has been going on for weeks jeffrey http://www.tweettronics.com
On Jul 10, 11:52 am, Matt Sanford <[email protected]> wrote: > Hi all, > > There is currently a back-end issue and our operation folks are > working on it. Hopefully it will be resolved soon. I'll update you > when I know more. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > On Jul 10, 2009, at 11:51 AM, João Pereira wrote: > > > > > Hi, > > > I'm also having some problems working with twitter API since the > > past few hours. Even with the Web interface I'm not able to complete > > a follow action, for example. > > > It's there anything going on? > > > On Fri, Jul 10, 2009 at 6:59 PM, Jeffrey Greenberg > > <[email protected] > > > wrote: > > > I'm not sure what these are but I see them often enough to wonder > > about the reliability of the network between Twitter and my app. The > > portion of my app the speaks with Twitter runs on Amazon AWS/EC2. I > > see a small variety of Curl failures that occur throughout the day. > > I'm not clear whether these reflect Twitter issues, EC2 issues, or my > > app. > > > I'd appreciate any illumination as to which of these might be Twitter > > issues and which are not... > > > I see 5 different Curl failures and take together with the various > > Twitter Api I am using, there 23 different variants all together. Here > > they are: > > > Curl error: 0. > > url:http://twitter.com/followers/ids.xml?user_id=18057710&page=1 > > Curl error: 0. url:http://twitter.com/followers/ids.xml?user_id=19966258 > > Curl error: 0. url:http://twitter.com/friends/ids.xml?user_id=14080067 > > Curl error: 0. > > url:http://twitter.com/friends/ids.xml?user_id=14623539&page=1 > > Curl error: 0. > > url:http://twitter.com/users/show.xml?screen_name=BryanMcKinney > > Curl error: 0. url:http://twitter.com/users/show.xml? > > user_id=10063932 > > Curl error: 7. couldn't connect to host url: > >http://search.twitter.com/search.json?q=neutrogena%20AND%20ultra%20sh... > > Curl error: 7. couldn't connect to host url: > >http://twitter.com/followers/ids.xml?user_id=11601722&page=1 > > Curl error: 7. couldn't connect to host url: > >http://twitter.com/followers/ids.xml?user_id=17825053 > > Curl error: 7. couldn't connect to host url: > >http://twitter.com/friends/ids.xml?user_id=13436432&page=1 > > Curl error: 7. couldn't connect to host > > url:http://twitter.com/friends/ids.xml?user_id=21937700 > > Curl error: 7. couldn't connect to host > > url:http://twitter.com/users/show.xml?screen_name=L4S7 > > Curl error: 7. couldn't connect to host > > url:http://twitter.com/users/show.xml?user_id=10108342 > > Curl error: 18. transfer closed with 150 bytes remaining to read url: > >http://twitter.com/users/show.xml?user_id=53631710 > > Curl error: 26. Failed to open/read local data from file/application > > url:http://twitter.com/friendships/create.xml?screen_name= > > /* OK this one is obviously a bug in my App */ > > Curl error: 26. Failed to open/read local data from file/application > > url:http://twitter.com/friendships/create.xml?screen_name=1WineDude > > Curl error: 52. Empty reply from server url: > >http://search.twitter.com/search.json?page=12&max_id=2500368394&rpp=1... > > Curl error: 52. Empty reply from server url: > >http://twitter.com/followers/ids.xml?user_id=11601722&page=1 > > Curl error: 52. Empty reply from server url: > >http://twitter.com/followers/ids.xml?user_id=15476479 > > Curl error: 52. Empty reply from server > > url:http://twitter.com/friends/ids.xml?user_id=27641196 > > Curl error: 52. Empty reply from server url: > >http://twitter.com/friends/ids.xml?user_id=37113325&page=1 > > Curl error: 52. Empty reply from server url: > >http://twitter.com/users/show.xml?screen_name=Cardenas79 > > Curl error: 52. Empty reply from server > > url:http://twitter.com/users/show.xml?user_id=1233581 > > ~ > > ~
