Matt will be conctacting you off-list. For future reference if others run into this issue: http://apiwiki.twitter.com/FAQ#IsmyIPbannedorblacklisted
On Wed, Feb 11, 2009 at 13:45, DustyReagan <[email protected]> wrote: > > Oh. I tested the API manually from home. Just typed the address in my > browser. > > On Feb 11, 3:32 pm, Matt Sanford <[email protected]> wrote: >> Hi Dusty, >> >> The timeout error sounds suspiciously like a network problem and >> not a rate limit issue. When you say you tested the API manually, did >> you do it from your servers? Also, if you can let me know the IP >> address I can check if it is blocked for some reason. >> >> Thanks; >> — Matt Sanford >> >> On Feb 11, 2009, at 01:29 PM, DustyReagan wrote: >> >> >> >> > PS. I'm using Media Temple to server my sites. Could the IP Address be >> > blocked or something? >> >> > On Feb 11, 3:27 pm, DustyReagan <[email protected]> wrote: >> >> Hi, >> >> >> I have 2 appshttp://FriendOrFollow.com(Ihaven't changed the code on >> >> this site in weeks) andhttp://FeaturedUsers.com(usesthe Zend >> >> Framework to access Twitter). Both of these sites are using the same >> >> authentication and are giving me the error "Unable to Connect to >> >> tcp://twitter.com:80. Error #110: Connection timed out." >> >> >> I've been checking my rate limit status quite a bit, and it doesn't >> >> seem to shift below 20k for some unknown reason. My rate limit right >> >> now is 19998 because I manually hit "http://twitter.com/statuses/ >> >> followers.xml" twice, just to see if the API was working. >> >> >> Did I miss a vital update to the API or something? What could be >> >> happening, that my apps are broken, but I can still manually hit the >> >> API? >> >> >> Thanks! >> >> >> Dusty > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
