Google App Engine blocked again

[Eliot Stock]

I notice the earlier thread on this is now locked (https://groups.google.com/forum/#!topic/mailchimp-api-discuss/MVpbELxQUE4). This continues to be a problem for me and presumably for everyone on GAE.

Jesse - Nilay is right. Your response to this would be appropriate ten years ago. Not now. We're in an era of cloud computing. If you're running your own server and are NOT on GAE, Azure, AWS or Salesforce.com, I would suggest you'll soon be the minority.

Mailchimp is going to have to take this seriously. A response such as 'contact our tech support with your IP address every time we block you and we'll unblock you' is not a solution.

Cheers,

Eliot.

[jesse]

Yup, I locked that thread because it has all of the necessary information to have the issue reported and potentially resovled, especially my last comment about the nature of any blocks our engineering team would have put in place.

Just for kicks, I checked for all of the previously blocked App Engine IPs and along with the netblocks Google's reports - none of it is blocked.

What you're both missing is that Cloud platforms are not the issue here - sharing source addresses with folks is.


jesse

[Eliot Stock]

I imagine sharing IP addresses across apps and cloud computing go hand in hand and this is not limited to GAE.

If I'm sharing an IP with another Mailchimp user and their app is misbehaving, why are you not blocking their API key rather than the whole IP for both of us? There may be a valid reason - I'm trying to understand the issue.

I would also point out that your error message in this situation is confusing and states that the API key is invalid or something to that effect.

[jesse]

I imagine sharing IP addresses across apps and cloud computing go hand in hand and this is not limited to GAE.

No, that is not necessarily the case.
 

If I'm sharing an IP with another Mailchimp user and their app is misbehaving, why are you not blocking their API key rather than the whole IP for both of us? There may be a valid reason - I'm trying to understand the issue.

We didn't block anything based on API usage. Had we, either we'd shut off connectivity completely, shut down the offending account(s), or disable the API key(s) involved - all of those things have been done.
 

I would also point out that your error message in this situation is confusing and states that the API key is invalid or something to that effect.

Abuse scenarios are often met with vague responses. What was the scenario? No clue, but again, the previous thread covers ways to have it investigated.


jesse