Thanks for the reply Vinny. 

No we are not using a reverse proxy, we operate a service that our 
customers can use so we have requests coming from all over world. Our 
customers have their own users so an individual customer may have many many 
thousands of users but we only see requests from our customer - i.e. the 
end user requests would be routed through our customer's servers before 
they reach us. We had two separate customers complain about this issue and 
that it was affecting their end users. Also, another customer who was doing 
> 300k requests per day suddenly stopped hitting our service, we are 
working with them to see if they also got blocked by Google.

Thanks for clarifying the blacklist in the Admin console - it would be very 
beneficial if Google did provide a way for us to see what traffic they are 
blocking! Rather than us waiting for our customers to complain!

I'm not sure where to take this now, I did finally get a response to my 
production ticket but it was marked as invalid :/ The reply said "it has 
most likely been blocked at the Google-wide level" with a link to 
here<http://support.google.com/websearch/answer/86640?hl=en>. So not terribly 
helpful.

Cheers,
Hamish









On Tuesday, 9 April 2013 17:58:15 UTC+1, Vinny P wrote:
>
> Whoa, you asked a lot of questions there! Taking it question by question:
>
>
> On Monday, April 8, 2013 3:37:42 AM UTC-5, Hamish wrote:
>>
>> We are getting reports from some of our users that they are getting 
>> blocked from making requests to our application on App Engine. They say 
>> they are getting the following message:
>>
>> "Our systems have detected unusual traffic from your computer network. 
>> Please try your request again later."
>>
>>
> Are you using a reverse proxy or some kind of automated service to query 
> Google/AppEngine? This can sometimes happen with those services. If you 
> are, you'll need to stop doing so and let Google's automated anti-DOS 
> systems unblock you.
> See here for a similar discussion: 
> https://groups.google.com/d/msg/google-appengine/ykW9HVjO1sk/C6V-R_03oBEJ 
>
>
> On Monday, April 8, 2013 3:37:42 AM UTC-5, Hamish wrote:
>>
>> The admin console blacklist in App Engine does not show us if anyone is 
>> blocked, should it?
>>
>
>  You're being blocked by Google's auto anti-DOS protection. That's an 
> entirely different service than the admin console blacklist. So no, it 
> shouldn't say anything (and remove it if it does).
>
>
> On Monday, April 8, 2013 3:37:42 AM UTC-5, Hamish wrote:
>>
>> Also, I created a post on Stackoverflow but it was closed as being "Off 
>> Topic" !!!
>>
>>
>> http://stackoverflow.com/questions/15835847/app-engine-blocking-users-due-to-unusual-traffic
>>
>
> Stack Overflow is for programming or other software development questions, 
> not server issues. For server questions, StackExchange maintains a separate 
> forum called Server Fault: http://serverfault.com/ 
> You may want to try reposting your question to that site.
>
> On Monday, April 8, 2013 3:42:45 AM UTC-5, Hamish wrote:
>>
>> Also - I'm not sure why this happened but the visibility of the 
>> production ticket I created was changed to "Only users with Commit 
>> permission can see this issue." last week for some reason.
>
>
> That's normal. It means that only Google employees can see your ticket. 
> Otherwise your ticket would have been available for all the world to see. 
>
> Just FYI, I'm not a Google employee, so I can't help you on this. You'll 
> just have to wait for support to get back to you.
>
>  
> -----------------
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> @GOV on AppDotNet: https://alpha.app.net/gov
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to