[twitter-dev] @Anywhere Login Timeouts
Hi, I've added a Twitter Connect (via @Anwhere) button to my test site and this all works great. However I've noticed that when I return to my site a few hrs later that I'm logged out and I have to click the Twitter Connect button again 1) Is this usual behaviour? 2) Can we increase the timeout anywhere? or disable it completely. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: @Anywhere Login Timeouts
While looking at localStorage in the browser, I noticed that when I connect with @anywhere various details are written to localStorage for my page including twitter_anywhere_cache_[account/verify_credentials,[]]_expiry: 1307546741323 twttr_anywhere_expiry: 1307552140184 which if interpreted as javascript Dates correspond to 30 minutes and 2 hours (respectively) after my connect time - that is 1800 * 000 and 7200 * 1000 ms. I haven't tried playing with them, but remembering that @anywhere is still largely experimental and undocumented, those keys might give you some thing to look for in the code and see if you can spot anything that looks like a valid way to tweak them. . -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: @Anywhere Login Timeouts
Thanks Tim. That does seem to correspond with what I'm seeing here. Hopefully it's something we'll be able to control eventually. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Twitter API Timeouts
Hi All -
Since early yesterday (India time) I have been seeing significant 403
errors -
Failed to search tweets: 403:The request is understood, but it has
been refused. An accompanying error message will explain why.
{error:since date or since_id is too old}
Neither of the above reasons is true since I poll about 2 times in a
minute and am only using a since_id since the last poll (at most a few
minutes old). Is there something else that has changed. This was
working fine till last weekend.
Thanks in advance for any reply.
Best
Rakesh
Using twitter search api via twitter4j
On Mar 1, 4:02 am, Colin Howe colintheh...@googlemail.com wrote:
Looks like it is working as normal again now...
Horrid way to find out our internal poller has a 10 minute timeout on
a request though :D
On Feb 28, 7:30 pm, Marc Mims marc.m...@gmail.com wrote:
* Taylor Singletary taylorsinglet...@twitter.com [110228 06:57]:
Thanks for the reports -- we're looking into the timeout issue.
I've been seeing this, too. To combat it, I've set my request timeout to
8 seconds and I use with Net::Twitter's RetryOnError trait (perl).
Last year, at Chrip, one of the speakers said Twitter's internal
strategy is to timeout quickly and re-queue. From my tests, it appears
requests normally fail in 4-5 seconds with a 502 if they can't be
fulfilled in that amount of time by the backend.
Taylor, can you confirm that? What is Twitter's internal cutoff? That
would help me set an optimum request timeout on my end.
FWIW, the Net::Twitter RetryOnError strategy is to retry any request
that fails with an HTTP status code = 500. It delays 250ms before the
first retry and doubles the retry delay until it gets to 4 seconds. If
it still can't get a successful return, it throws an error at that
point.
-Marc- Hide quoted text -
- Show quoted text -
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Twitter API Timeouts
Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Twitter API Timeouts
We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no timeout set.. I am also curious if there was a change made that would be attributed to this change in behavior. --Naveen On Feb 28, 2:14 am, Colin Howe colintheh...@googlemail.com wrote: Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter API Timeouts
Hi, I have noticed the same behaviour today, connections time out after 30 seconds, even the verify_credentials api call fails... the api status page shows everything is fine though. Regards, Leon Meijer _ From: Naveen [mailto:knig...@gmail.com] To: Twitter Development Talk [mailto:twitter-development-talk@googlegroups.com] Sent: Mon, 28 Feb 2011 11:36:57 +0100 Subject: [twitter-dev] Re: Twitter API Timeouts We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no timeout set.. I am also curious if there was a change made that would be attributed to this change in behavior. --Naveen On Feb 28, 2:14 am, Colin Howe colintheh...@googlemail.com wrote: Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter API Timeouts
Hi, Even echofon clients are timing out. It coul be a general failure of service. Let us see if Twitter wants to clarify Regards Umashankar Das On Mon, Feb 28, 2011 at 5:13 PM, Leon Meijer l...@lmeijer.nl wrote: Hi, I have noticed the same behaviour today, connections time out after 30 seconds, even the verify_credentials api call fails... the api status page shows everything is fine though. Regards, Leon Meijer -- *From:* Naveen [mailto:knig...@gmail.com] *To:* Twitter Development Talk [mailto: twitter-development-talk@googlegroups.com] *Sent:* Mon, 28 Feb 2011 11:36:57 +0100 *Subject:* [twitter-dev] Re: Twitter API Timeouts We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no timeout set.. I am also curious if there was a change made that would be attributed to this change in behavior. --Naveen On Feb 28, 2:14 am, Colin Howe colintheh...@googlemail.com wrote: Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter API Timeouts
Hi all, Thanks for the reports -- we're looking into the timeout issue. Taylor On Mon, Feb 28, 2011 at 4:43 AM, Umashankar Das umashankar...@gmail.comwrote: Hi, Even echofon clients are timing out. It coul be a general failure of service. Let us see if Twitter wants to clarify Regards Umashankar Das On Mon, Feb 28, 2011 at 5:13 PM, Leon Meijer l...@lmeijer.nl wrote: Hi, I have noticed the same behaviour today, connections time out after 30 seconds, even the verify_credentials api call fails... the api status page shows everything is fine though. Regards, Leon Meijer -- *From:* Naveen [mailto:knig...@gmail.com] *To:* Twitter Development Talk [mailto: twitter-development-talk@googlegroups.com] *Sent:* Mon, 28 Feb 2011 11:36:57 +0100 *Subject:* [twitter-dev] Re: Twitter API Timeouts We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no timeout set.. I am also curious if there was a change made that would be attributed to this change in behavior. --Naveen On Feb 28, 2:14 am, Colin Howe colintheh...@googlemail.com wrote: Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter API Timeouts
* Taylor Singletary taylorsinglet...@twitter.com [110228 06:57]: Thanks for the reports -- we're looking into the timeout issue. I've been seeing this, too. To combat it, I've set my request timeout to 8 seconds and I use with Net::Twitter's RetryOnError trait (perl). Last year, at Chrip, one of the speakers said Twitter's internal strategy is to timeout quickly and re-queue. From my tests, it appears requests normally fail in 4-5 seconds with a 502 if they can't be fulfilled in that amount of time by the backend. Taylor, can you confirm that? What is Twitter's internal cutoff? That would help me set an optimum request timeout on my end. FWIW, the Net::Twitter RetryOnError strategy is to retry any request that fails with an HTTP status code = 500. It delays 250ms before the first retry and doubles the retry delay until it gets to 4 seconds. If it still can't get a successful return, it throws an error at that point. -Marc -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnot able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnot able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotable to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotableto connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
It's been a long time, I'm completely helpless in this. Please look into it soon and help me out, I have thousands of users who visit the site everyday, been receiving a lot of mails and tweets regarding the errors. -Nischal On Sep 28, 1:41 pm, nischalshetty nischalshett...@gmail.com wrote: @John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotabletoconnect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
Are you still experiencing problems? We've checked our systems and have checked GAE isn't blocked. Best, @themattharris On Sep 28, 2010, at 9:23, nischalshetty nischalshett...@gmail.com wrote: It's been a long time, I'm completely helpless in this. Please look into it soon and help me out, I have thousands of users who visit the site everyday, been receiving a lot of mails and tweets regarding the errors. -Nischal On Sep 28, 1:41 pm, nischalshetty nischalshett...@gmail.com wrote: @John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotabletoconnect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@Matt thanks a lot. Not seeing the timeouts any more. 500s are everywhere but I understand from your status blog it's a known thing. Thanks for all the help. Over the Appengine group, we've been discussing about IP blocking for cloud offerings like GAE. Would you be able to help with this? Similar thing happened 2 months ago when Appengine apps were all blocked. It lasted for a long time back then as well. Would you guys not be able to allow apps that send their consumer secret and token with the requests? One rogue app on the GAE causes all other good apps to stop working. GAE is one of the best things that has happened to small time devs like me but it has its own limitations and shared IPs are one of them. But I'm pretty sure you guys at Twitter would be able to find a workaround to help us in this problem. -Nischal On Sep 29, 5:59 am, Matt Harris mhar...@twitter.com wrote: Are you still experiencing problems? We've checked our systems and have checked GAE isn't blocked. Best, @themattharris On Sep 28, 2010, at 9:23, nischalshetty nischalshett...@gmail.com wrote: It's been a long time, I'm completely helpless in this. Please look into it soon and help me out, I have thousands of users who visit the site everyday, been receiving a lot of mails and tweets regarding the errors. -Nischal On Sep 28, 1:41 pm, nischalshetty nischalshett...@gmail.com wrote: @John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotabletoconnectto Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer
[twitter-dev] Not able to connect to twitter through Google Appengine, getting Timeouts
My app http://www.justunfollow.com is not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Not able to connect to twitter through Google Appengine, getting Timeouts
We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My app http://www.justunfollow.com is not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comis not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comis not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: High frequency of search API timeouts
Thanks for confirming. Glad I'm not alone! Are you using the source keyword in your queries? The more I try, the more I think that seems to be the problem since I can't recreate timeouts/long query times when I don't use it. But again, maybe not I'll work on not using it for now. But, thought I'd mention in case anybody from the twitter search team is out there. Nice app BTW, looks cool. rw On Apr 14, 8:56 am, Pykler hnass...@gmail.com wrote: I am a member of a team working on a new startup to classify twittersearchresults into various categories. Kinda cool, check itouthttp://twecan.com/. However, not all queries may work, and sometimes you would have to resubmit them as mentioned by Ryan. On Apr 12, 7:04 pm, Ryan W rwilli...@gmail.com wrote: Is anybody else seeing a high frequency ofsearchtimeouts? ... Seemed to be working fine until yesterday. YES! same thing. Here's the weird part though. First case: - execute complexsearchdirectly in browser and it timesoutlike my app gets on App Engine Second case: - run a simple, single word,searchin a browser - then run the complexsearchimmediately after and it works It's almost like it has to be primed? It also seems like the -source parameter is the problem, but that could just be anecdotal and clouded by my second case example above. To me it looked random, re-running the same query seems to work sometimes and then fail. We thought it was our caching strategy which we worked all night yesterday optimizing so that we don't hit twittersearchas much, yet we often get timedout. Wonder if someone is looking into this. -- Hatem Twecan Developerhttp://twecan.com- Twecan - Making sense of twittersearch -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: High frequency of search API timeouts
There is a known issue with source and the search api that will be fixed on the search deploy next week. Jonathan On Wed, Apr 14, 2010 at 8:24 PM, Ryan W rwilli...@gmail.com wrote: Thanks for confirming. Glad I'm not alone! Are you using the source keyword in your queries? The more I try, the more I think that seems to be the problem since I can't recreate timeouts/long query times when I don't use it. But again, maybe not I'll work on not using it for now. But, thought I'd mention in case anybody from the twitter search team is out there. Nice app BTW, looks cool. rw On Apr 14, 8:56 am, Pykler hnass...@gmail.com wrote: I am a member of a team working on a new startup to classify twittersearchresults into various categories. Kinda cool, check itouthttp:// twecan.com/. However, not all queries may work, and sometimes you would have to resubmit them as mentioned by Ryan. On Apr 12, 7:04 pm, Ryan W rwilli...@gmail.com wrote: Is anybody else seeing a high frequency ofsearchtimeouts? ... Seemed to be working fine until yesterday. YES! same thing. Here's the weird part though. First case: - execute complexsearchdirectly in browser and it timesoutlike my app gets on App Engine Second case: - run a simple, single word,searchin a browser - then run the complexsearchimmediately after and it works It's almost like it has to be primed? It also seems like the -source parameter is the problem, but that could just be anecdotal and clouded by my second case example above. To me it looked random, re-running the same query seems to work sometimes and then fail. We thought it was our caching strategy which we worked all night yesterday optimizing so that we don't hit twittersearchas much, yet we often get timedout. Wonder if someone is looking into this. -- Hatem Twecan Developerhttp://twecan.com- Twecan - Making sense of twittersearch -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] High frequency of search API timeouts
Is anybody else seeing a high frequency of search timeouts? I have a periodic search with 6 keyword ORs and 3 negating attributes (i.e. -from=, -source=, -RT) Seemed to be working fine until yesterday. Here's the weird part though. First case: - execute complex search directly in browser and it times out like my app gets on App Engine Second case: - run a simple, single word, search in a browser - then run the complex search immediately after and it works It's almost like it has to be primed? It also seems like the -source parameter is the problem, but that could just be anecdotal and clouded by my second case example above. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Timeouts and API Errors, Tuesday August 11th
We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
I have a spare bazooka in my basement. Let me know. I can FedEx it to you. Dewald On Aug 11, 4:23 pm, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
I'm so happy gmail has a star feature, that deserved one. Tim. On Wed, Aug 12, 2009 at 7:28 AM, Dewald Pretoriusdpr...@gmail.com wrote: I have a spare bazooka in my basement. Let me know. I can FedEx it to you. Dewald On Aug 11, 4:23 pm, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
On Tue, Aug 11, 2009 at 4:11 PM, Alex Paynea...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x Has it resumed? Still getting lots of intermittency here. ∞ 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: Timeouts and API Errors, Tuesday August 11th
My guess is it's still ongoing. I'm seeing far more rejections per second, and the number of backed-off retries have also increased. Dewald On Aug 11, 5:37 pm, Andrew Badera and...@badera.us wrote: On Tue, Aug 11, 2009 at 4:11 PM, Alex Paynea...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x Has it resumed? Still getting lots of intermittency here. ∞ 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: Timeouts and API Errors, Tuesday August 11th
Yes, I've just been informed that the attack has resumed, and that our service provider is putting network hardware in place to counter the attack. We're trying to work with them to ensure minimal impact to the API, but in the near term there may be issues with OAuth and the Streaming API. This is a bit of a juggling act, as we're trying to coordinate our team, the operations team, our service provider's staff, and specialists that they've brought in for this issue. Please bear with us. On Tue, Aug 11, 2009 at 13:54, Dewald Pretorius dpr...@gmail.com wrote: My guess is it's still ongoing. I'm seeing far more rejections per second, and the number of backed-off retries have also increased. Dewald On Aug 11, 5:37 pm, Andrew Badera and...@badera.us wrote: On Tue, Aug 11, 2009 at 4:11 PM, Alex Paynea...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x Has it resumed? Still getting lots of intermittency here. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne a...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
We're aware of these issues; sorry. Our ops team tells me that the countermeasures that are being put in place should not cause the 302 redirect behavior that impacted OAuth and other services late last week. If you're seeing that behavior, please post here and we'll coordinate with them to eliminate it. On Tue, Aug 11, 2009 at 13:58, Sean Callahan seancalla...@gmail.com wrote: Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne a...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Also, please be sure to provide packet dumps and full headers where possible so we can more easily determine the source of the issue. Thanks, Ryan On Tue, Aug 11, 2009 at 2:00 PM, Alex Paynea...@twitter.com wrote: We're aware of these issues; sorry. Our ops team tells me that the countermeasures that are being put in place should not cause the 302 redirect behavior that impacted OAuth and other services late last week. If you're seeing that behavior, please post here and we'll coordinate with them to eliminate it. On Tue, Aug 11, 2009 at 13:58, Sean Callahan seancalla...@gmail.com wrote: Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne a...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
On Tue, Aug 11, 2009 at 5:01 PM, Andrew Baderaand...@badera.us wrote: On Tue, Aug 11, 2009 at 4:57 PM, Alex Paynea...@twitter.com wrote: Yes, I've just been informed that the attack has resumed, and that our service provider is putting network hardware in place to counter the attack. We're trying to work with them to ensure minimal impact to the API, but in the near term there may be issues with OAuth and the Streaming API. This is a bit of a juggling act, as we're trying to coordinate our team, the operations team, our service provider's staff, and specialists that they've brought in for this issue. Please bear with us. Thanks for the update Alex. No worries here, you all seem to be keeping us much more comfortably updated than most of Friday. --ab *Thursday, not Friday
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Just found out that our hosting provider put some hardware in place that may cause disruptions. Our operations team just spoke them, and they should be taking it down in 15 - 30 minutes. On Tue, Aug 11, 2009 at 14:03, Andrew Badera and...@badera.us wrote: On Tue, Aug 11, 2009 at 5:01 PM, Andrew Baderaand...@badera.us wrote: On Tue, Aug 11, 2009 at 4:57 PM, Alex Paynea...@twitter.com wrote: Yes, I've just been informed that the attack has resumed, and that our service provider is putting network hardware in place to counter the attack. We're trying to work with them to ensure minimal impact to the API, but in the near term there may be issues with OAuth and the Streaming API. This is a bit of a juggling act, as we're trying to coordinate our team, the operations team, our service provider's staff, and specialists that they've brought in for this issue. Please bear with us. Thanks for the update Alex. No worries here, you all seem to be keeping us much more comfortably updated than most of Friday. --ab *Thursday, not Friday -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
For me the API behavior is now back again to this morning, with around 2 to 5 rejections per second, and most being successful on the first or second backed-off retry. Dewald On Aug 11, 6:22 pm, Alex Payne a...@twitter.com wrote: Just found out that our hosting provider put some hardware in place that may cause disruptions. Our operations team just spoke them, and they should be taking it down in 15 - 30 minutes. On Tue, Aug 11, 2009 at 14:03, Andrew Badera and...@badera.us wrote: On Tue, Aug 11, 2009 at 5:01 PM, Andrew Baderaand...@badera.us wrote: On Tue, Aug 11, 2009 at 4:57 PM, Alex Paynea...@twitter.com wrote: Yes, I've just been informed that the attack has resumed, and that our service provider is putting network hardware in place to counter the attack. We're trying to work with them to ensure minimal impact to the API, but in the near term there may be issues with OAuth and the Streaming API. This is a bit of a juggling act, as we're trying to coordinate our team, the operations team, our service provider's staff, and specialists that they've brought in for this issue. Please bear with us. Thanks for the update Alex. No worries here, you all seem to be keeping us much more comfortably updated than most of Friday. --ab *Thursday, not Friday -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] XML Timeouts
I'm receiving timeouts when using this script today. I'm looking for anyone else having this problem today and looked for any status updates but I haven't seen anything. This script has always worked except for today. Can anyone give any advice? error: msxml3.dll error '80072ee2' The operation timed out Set xml = Server.CreateObject(MSXML2.XMLHTTP) twitter_username = thisisit 'change to your twitter username twitter_password = thisismypassword 'change to your twitter password new_status = title urltowrite 'change to your new status xml.Open POST, http://; twitter_username : twitter_password @twitter.com/statuses/update.xml?status= server.URLencode (new_status), False xml.setRequestHeader Content-Type, content=text/html; charset=iso-8859-1 xml.Send
[twitter-dev] Re: API Disconnections Timeouts
I get it in particular on some of the really big Twitter accounts. It would be really nice to have a solution to this. All I can tell them is Twitter's broken - I hate doing that. Jesse On Sun, Apr 19, 2009 at 7:31 PM, Dossy Shiobara do...@panoptic.com wrote: On 4/19/09 8:32 PM, LeeS wrote: Lately, I've been getting a lot of both immediate disconnections or long timeouts, when trying to issue API calls. This is from a whitelisted Twitter account so rate limiting isn't the issue. I reported this last week in my Twitter API returning truncated XML responses[1] thread. [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/aee5785a56c3b56d/e86e49041a57e658 Everyone who's seeing this issue, please chime in - this way, the Twitter Ops folks can see how many third-party app. developers are being affected by this. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: Timeouts
Alex, is this issue fully resolved? Right now I cannot connect to twitter.com any more from certain hosts. It works from others. The host in question is api.twibble.de (80.83.114.92) which used to work fine over the last months. curl http://twitter.com curl: (7) couldn't connect to host Thanks, Thilo On Oct 28, 7:01 pm, Alex Payne [EMAIL PROTECTED] wrote: We're noticing highnetworklatency and timeouts on twitter.com today, which some of you are probably noticing in your apps. The problem doesn't appear to be within our cluster, and we're working with our service provider to sort it out. We'll be tracking the issue onhttp://status.twitter.com/. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Timeouts
Yes, this issue was resolved. Additionally, we put a higher-capacity firewall in place since that network event. On Thu, Nov 6, 2008 at 12:02 AM, twibble [EMAIL PROTECTED] wrote: Alex, is this issue fully resolved? Right now I cannot connect to twitter.com any more from certain hosts. It works from others. The host in question is api.twibble.de (80.83.114.92) which used to work fine over the last months. curl http://twitter.com curl: (7) couldn't connect to host Thanks, Thilo On Oct 28, 7:01 pm, Alex Payne [EMAIL PROTECTED] wrote: We're noticing highnetworklatency and timeouts on twitter.com today, which some of you are probably noticing in your apps. The problem doesn't appear to be within our cluster, and we're working with our service provider to sort it out. We'll be tracking the issue onhttp://status.twitter.com/. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Timeouts
We're noticing high network latency and timeouts on twitter.com today, which some of you are probably noticing in your apps. The problem doesn't appear to be within our cluster, and we're working with our service provider to sort it out. We'll be tracking the issue on http://status.twitter.com/. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
