[twitter-dev] Re: Issues with the API this morning?
Any update on the random 408 errors. I'm still having frequent issues. On Aug 17, 2:13 pm, Alex Payne wrote: > Just sent out an update on the sort of information we need to help you > guys out. We're working on it. Expect things to open up for a bit as > we tune some settings for the next hour. > > > > > > On Mon, Aug 17, 2009 at 12:07, Sean P. wrote: > > > I was starting to worry that something was wrong with Twobile (basic > > auth). Any news from the mothership on what's happening? > > > On Aug 17, 10:42 am, Aaron Forgue wrote: > >> My app, too, appears to be blocked. I can't even get status codes - > >> the requests just timeout with no response. > > >> On Aug 17, 12:24 pm, Dewald Pretorius wrote: > > >> > So, the general message is: Mayhem rules. > > >> > I have no issues with Basic Auth (on low volume API calls). Login no > >> > problem. > > >> > Dewald > > >> > On Aug 17, 1:04 pm, Sean Callahan wrote: > > >> > > The issue we're seeing at TweetPhoto is that no one can login to their > >> > > account when using basic auth. Was informed by Twitter support that > >> > > they are aware of the issue and are looking for a fix. > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Issues with the API this morning?
Just sent out an update on the sort of information we need to help you guys out. We're working on it. Expect things to open up for a bit as we tune some settings for the next hour. On Mon, Aug 17, 2009 at 12:07, Sean P. wrote: > > I was starting to worry that something was wrong with Twobile (basic > auth). Any news from the mothership on what's happening? > > On Aug 17, 10:42 am, Aaron Forgue wrote: >> My app, too, appears to be blocked. I can't even get status codes - >> the requests just timeout with no response. >> >> On Aug 17, 12:24 pm, Dewald Pretorius wrote: >> >> > So, the general message is: Mayhem rules. >> >> > I have no issues with Basic Auth (on low volume API calls). Login no >> > problem. >> >> > Dewald >> >> > On Aug 17, 1:04 pm, Sean Callahan wrote: >> >> > > The issue we're seeing at TweetPhoto is that no one can login to their >> > > account when using basic auth. Was informed by Twitter support that >> > > they are aware of the issue and are looking for a fix. >> >> > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Issues with the API this morning?
I was starting to worry that something was wrong with Twobile (basic auth). Any news from the mothership on what's happening? On Aug 17, 10:42 am, Aaron Forgue wrote: > My app, too, appears to be blocked. I can't even get status codes - > the requests just timeout with no response. > > On Aug 17, 12:24 pm, Dewald Pretorius wrote: > > > So, the general message is: Mayhem rules. > > > I have no issues with Basic Auth (on low volume API calls). Login no > > problem. > > > Dewald > > > On Aug 17, 1:04 pm, Sean Callahan wrote: > > > > The issue we're seeing at TweetPhoto is that no one can login to their > > > account when using basic auth. Was informed by Twitter support that > > > they are aware of the issue and are looking for a fix. > >
[twitter-dev] Re: Issues with the API this morning?
My app, too, appears to be blocked. I can't even get status codes - the requests just timeout with no response. On Aug 17, 12:24 pm, Dewald Pretorius wrote: > So, the general message is: Mayhem rules. > > I have no issues with Basic Auth (on low volume API calls). Login no > problem. > > Dewald > > On Aug 17, 1:04 pm, Sean Callahan wrote: > > > The issue we're seeing at TweetPhoto is that no one can login to their > > account when using basic auth. Was informed by Twitter support that > > they are aware of the issue and are looking for a fix.
[twitter-dev] Re: Issues with the API this morning?
So, the general message is: Mayhem rules. I have no issues with Basic Auth (on low volume API calls). Login no problem. Dewald On Aug 17, 1:04 pm, Sean Callahan wrote: > The issue we're seeing at TweetPhoto is that no one can login to their > account when using basic auth. Was informed by Twitter support that > they are aware of the issue and are looking for a fix.
[twitter-dev] Re: Issues with the API this morning?
The issue we're seeing at TweetPhoto is that no one can login to their account when using basic auth. Was informed by Twitter support that they are aware of the issue and are looking for a fix. On Aug 17, 8:53 am, Dewald Pretorius wrote: > Lots of issues here (tweetlater) too. High-volume calls are again > blocked by the edge defenses with connection refused. > > Exactly the same as last weekend. > > Dewald > > On Aug 17, 12:19 pm, CodeWarden wrote: > > > > > Are there still issues with the API this morning? We have many of our > > UberTwitter users reporting timeouts when trying to retrieve timelines > > and send tweets. We are not using OAUTH. > > > Any info would be greatly appreciated! > > > -CodeWarden
[twitter-dev] Re: Issues with the API this morning?
Lots of issues here (tweetlater) too. High-volume calls are again blocked by the edge defenses with connection refused. Exactly the same as last weekend. Dewald On Aug 17, 12:19 pm, CodeWarden wrote: > Are there still issues with the API this morning? We have many of our > UberTwitter users reporting timeouts when trying to retrieve timelines > and send tweets. We are not using OAUTH. > > Any info would be greatly appreciated! > > -CodeWarden
[twitter-dev] Re: Issues with the API this morning?
On Mon, Aug 17, 2009 at 11:25 AM, Mario Menti wrote: > Same here (twitterfeed), we're getting very large numbers (tens of > thousands) of 500 timeout errors on status updates. Although the extent > isn't quite as bad, the symptoms and messages look like they did during the > DDoS attack, so I suspect they are again throttling/blocking some > high-volume apps. > Mario. > > On Mon, Aug 17, 2009 at 4:19 PM, CodeWarden wrote: >> >> Are there still issues with the API this morning? We have many of our >> UberTwitter users reporting timeouts when trying to retrieve timelines >> and send tweets. We are not using OAUTH. >> >> Any info would be greatly appreciated! >> >> -CodeWarden > > Also been seeing occasional failed page loads on the web. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
[twitter-dev] Re: Issues with the API this morning?
Same here (twitterfeed), we're getting very large numbers (tens of thousands) of 500 timeout errors on status updates. Although the extent isn't quite as bad, the symptoms and messages look like they did during the DDoS attack, so I suspect they are again throttling/blocking some high-volume apps. Mario. On Mon, Aug 17, 2009 at 4:19 PM, CodeWarden wrote: > > Are there still issues with the API this morning? We have many of our > UberTwitter users reporting timeouts when trying to retrieve timelines > and send tweets. We are not using OAUTH. > > Any info would be greatly appreciated! > > -CodeWarden >
